Triple
T3305285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Armenia |
E69432
|
entity |
| Predicate | torse |
P47930
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Coat of arms of Armenia, torse, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: torse Context triple: [Coat of arms of Armenia, torse, none]
-
A.
seatOfBody
Indicates that one entity serves as the physical location or base where another entity (typically an organization or authority) is situated or headquartered.
-
B.
bodyFusedWith
Indicates that two or more bodies or physical structures are joined together into a single, continuous unit.
-
C.
bodyVariant
Indicates that one entity is an alternative physical form or version of another entity’s body.
-
D.
tension
Indicates a state of strain, stress, or conflict existing between entities, often involving opposing forces, interests, or emotions.
-
E.
hasBodyRegion
Indicates that an entity possesses, includes, or is associated with a specific anatomical or bodily region.
- F. None of above. chosen
Provenance (4 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_69ad859f218081909458d2cebbf57565 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0c9470881908c36c1984fdbb67b |
completed | March 8, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada526764881908e4bd52938d5374d |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:11 p.m.