Triple
T1348767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States coat of arms |
E28831
|
entity |
| Predicate | eagleOrientation |
P3338
|
FINISHED |
| Object | eagle faces olive branch |
—
|
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: eagle faces olive branch | Statement: [United States coat of arms, eagleOrientation, eagle faces olive branch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eagleOrientation Context triple: [United States coat of arms, eagleOrientation, eagle faces olive branch]
-
A.
eagleFaces
chosen
Indicates that an eagle is oriented toward, looking at, or facing another entity or direction.
-
B.
legOrientation
Indicates the relative positioning or directional alignment of an entity’s leg(s) with respect to a reference frame or another object.
-
C.
shaftOrientation
Indicates the directional alignment or angle at which a shaft is positioned or oriented relative to a reference frame or object.
-
D.
hasRunwayOrientation
Indicates that a runway is aligned or oriented in a specific directional heading.
-
E.
orientation
Indicates the relative directional alignment or facing of one entity with respect to another or to a reference frame.
- 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c268745481908be649526c18e558 |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef5857c81909ae984feb85a26ca |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.