Triple
T366979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Half Eagle |
E7981
|
entity |
| Predicate | reverseDesignType |
P1603
|
FINISHED |
| Object | Heraldic eagle (various types) |
—
|
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: Heraldic eagle (various types) | Statement: [Half Eagle, reverseDesignType, Heraldic eagle (various types)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reverseDesignType Context triple: [Half Eagle, reverseDesignType, Heraldic eagle (various types)]
-
A.
reversed
Indicates that the direction or order of a previously defined relationship or sequence between entities is inverted.
-
B.
badgeReverseDesign
chosen
Indicates the design or imagery that appears on the reverse (back) side of a badge.
-
C.
redesigned
Indicates that an entity has been modified or created anew in terms of its structure, appearance, or functionality, replacing a previous design.
-
D.
reverseInscription
Indicates that one entity is inscribed as the reverse or mirror image of another entity’s inscription.
-
E.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebe92c7c8190b49af2b2b461eacc |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95ede588190998fdf3a6ea90498 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.