Triple
T31015237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neogranadine |
E790310
|
entity |
| Predicate | successorDemonyms |
P62943
|
FINISHED |
| Object | Colombian |
—
|
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: Colombian | Statement: [Neogranadine, successorDemonyms, Colombian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorDemonyms Context triple: [Neogranadine, successorDemonyms, Colombian]
-
A.
successorNamesake
Indicates that one entity is named after another entity that precedes it, typically as its successor or continuation in name.
-
B.
successorEnglishName
Indicates that one entity’s English name is the direct successor or replacement of another entity’s English name.
-
C.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
-
D.
ethnicSuccessor
chosen
Indicates that one ethnic group is the successor or continuation of another, typically inheriting its identity, culture, or population in a historical or social sense.
-
E.
successorSee
Indicates that one entity assumes or continues the role, position, or function previously held by another.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
Created at: April 29, 2026, 8:57 p.m.