Triple
T23055711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plano de Metas |
E574149
|
entity |
| Predicate | includedProject |
P150802
|
FINISHED |
| Object | construction of Brasília |
—
|
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: construction of Brasília | Statement: [Plano de Metas, includedProject, construction of Brasília]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedProject Context triple: [Plano de Metas, includedProject, construction of Brasília]
-
A.
hasProjectIn
Indicates that an entity is involved with or associated with a project that takes place within a specified location or context.
-
B.
intendedProject
Indicates that an entity is the planned or targeted project associated with another entity (such as a person, organization, or activity).
-
C.
usedInProject
Indicates that something (such as a resource, tool, or component) is employed or utilized within a particular project.
-
D.
eligibleProject
Indicates that a project satisfies the required conditions or criteria to qualify for a particular status, process, or benefit.
-
E.
isSisterProjectOf
Indicates that two projects are related and aligned in purpose or scope, typically operating in parallel under a common umbrella or organization.
- 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_69e245ba7ae48190be606dbc54120e39 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1867f71508190ad4513c6de2453e6 |
completed | April 29, 2026, 4:18 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 3:55 p.m.