Triple
T24422624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Uruguay |
E615764
|
entity |
| Predicate | montevideoFoundationYear |
P4025
|
FINISHED |
| Object | 1726 |
—
|
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: 1726 | Statement: [History of Uruguay, montevideoFoundationYear, 1726]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: montevideoFoundationYear Context triple: [History of Uruguay, montevideoFoundationYear, 1726]
-
A.
isFoundedOn
Indicates that one entity is established, created, or based upon another entity as its foundational source or principle.
-
B.
portrayedAsFoundedIn
Indicates that an entity is depicted or represented as having been founded in a particular time or place, regardless of historical accuracy.
-
C.
governingBodyFoundedIn
Indicates that a governing body was established or came into official existence in a specified year or time period.
-
D.
foundedOn
Indicates that an entity was established, created, or brought into existence on a specific date or point in time.
-
E.
foundedAt
chosen
Indicates the time or date at which an entity (such as an organization, project, or institution) was established or created.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a4285881909376560f1cf4bf62 |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:14 a.m.