Triple
T388102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexican national coat of arms |
E8820
|
entity |
| Predicate | serpentPosition |
P5132
|
FINISHED |
| Object | held in the eagle’s beak and talon |
—
|
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: held in the eagle’s beak and talon | Statement: [Mexican national coat of arms, serpentPosition, held in the eagle’s beak and talon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serpentPosition Context triple: [Mexican national coat of arms, serpentPosition, held in the eagle’s beak and talon]
-
A.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
B.
positionOnTrident
Indicates that one entity occupies a specific location or slot on a trident-like structure or configuration.
-
C.
positionB
chosen
Indicates that one entity occupies or is located at a specific position relative to another entity.
-
D.
positionA
Indicates the spatial or ordered position of an entity A within a defined reference frame or sequence.
-
E.
hasPositionOn
Indicates that one entity occupies or holds a specific role, job, or spatial location relative to 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec5988708190aa86d9460cecf050 |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e967d84c8190a6b647f78d95d4e4 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.