Triple
T27497816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of Rionegro of 1863 |
E694062
|
entity |
| Predicate | definedEntity |
P79651
|
FINISHED |
| Object | United States of Colombia |
—
|
NE NERFINISHED |
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: United States of Colombia | Statement: [Constitution of Rionegro of 1863, definedEntity, United States of Colombia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedEntity Context triple: [Constitution of Rionegro of 1863, definedEntity, United States of Colombia]
-
A.
definesEntity
chosen
Indicates that one entity specifies, determines, or establishes the identity, nature, or boundaries of another entity.
-
B.
defined
Indicates that one entity specifies, explains, or establishes the meaning, scope, or identity of another entity.
-
C.
definitionType
Indicates the specific kind or category of definition that characterizes how one entity is defined in relation to another.
-
D.
boundEntity
Indicates that one entity is constrained, tied, or otherwise held in a fixed relationship or dependency to another entity.
-
E.
establishedEntity
Indicates that one entity formally founded, created, or set up another entity, such as an organization, institution, or system.
- 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 27, 2026, 1:09 p.m.