Triple
T12672762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presidential Standard of Colombia |
E302727
|
entity |
| Predicate | rankIndication |
P15589
|
FINISHED |
| Object | indicates rank of head of state |
—
|
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: indicates rank of head of state | Statement: [Presidential Standard of Colombia, rankIndication, indicates rank of head of state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankIndication Context triple: [Presidential Standard of Colombia, rankIndication, indicates rank of head of state]
-
A.
rankIndicated
chosen
Indicates that one entity specifies, denotes, or reveals the hierarchical rank or level of another entity.
-
B.
rankStatus
Indicates the hierarchical level or position an entity holds within an ordered ranking or status system.
-
C.
rankFlagFor
Indicates that something is assigned or associated with a specific ranking flag used to mark its status or priority.
-
D.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
E.
rankSignificance
Indicates how important or influential one entity is relative to others within a specified context or ordering.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:20 p.m.