Triple
T2849673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States double eagle |
E63061
|
entity |
| Predicate | notableVariety |
P41829
|
FINISHED |
| Object | 1849 double eagle pattern |
—
|
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: 1849 double eagle pattern | Statement: [United States double eagle, notableVariety, 1849 double eagle pattern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVariety Context triple: [United States double eagle, notableVariety, 1849 double eagle pattern]
-
A.
typicalVariety
Indicates that one entity is a representative or characteristic example of the variety or type defined by another entity.
-
B.
varietyOf
chosen
Indicates that one entity is a specific type, kind, or variant of another, more general entity.
-
C.
notableSpecies
Indicates that the subject is known for, or significantly associated with, the specified species.
-
D.
notableTreeSpecies
Indicates that the subject place or area is known for, or characterized by, the specified tree species.
-
E.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
- 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf41ac24819087c5b72e3b84117c |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd0e86808190bcefffafbd3cd441 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.