Triple
T12513900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liberty Head (Type 1) |
E299148
|
entity |
| Predicate | designTypeNumber |
P3378
|
FINISHED |
| Object | Type 1 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Type 1 | Statement: [Liberty Head (Type 1), designTypeNumber, Type 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designTypeNumber Context triple: [Liberty Head (Type 1), designTypeNumber, Type 1]
-
A.
designedStructureType
Indicates the type or category of structure that something has been specifically designed to be.
-
B.
designatorType
Indicates the specific role or category of a designator used to identify or reference an entity within a system or context.
-
C.
numberingType
chosen
Indicates the scheme or style used to assign sequential numbers or labels within an ordered set.
-
D.
designStandardizedIn
Indicates that something is designed according to the rules, formats, or specifications defined within a particular standard or standardization framework.
-
E.
designModel
Indicates that one entity creates, specifies, or defines the structure or behavior of another entity as a model or blueprint.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.