Triple
T34058798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBSA Dialogue Forum |
E873434
|
entity |
| Predicate | foundingMeetingLocation |
P55364
|
FINISHED |
| Object | Brasilia |
—
|
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: Brasilia | Statement: [IBSA Dialogue Forum, foundingMeetingLocation, Brasilia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingMeetingLocation Context triple: [IBSA Dialogue Forum, foundingMeetingLocation, Brasilia]
-
A.
foundingLocationOfFoundedOrganization
chosen
Indicates the place where an organization was originally established or founded.
-
B.
capitalOfMeetingPlace
Indicates that a location serves as the capital city where a particular meeting or set of meetings takes place.
-
C.
firstConstitutionalConventionLocation
Indicates the place where an entity’s first constitutional convention was held.
-
D.
headquartersFoundedAt
Indicates that an organization's headquarters was originally established at a specific location.
-
E.
headquartersLocationOfFoundedOrganization
Indicates that a location serves as the headquarters of an organization that was founded there.
- 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_69f349a4af208190afa14888f9c9fb9d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69feb5e66224819083b87c3707a5a5e0 |
completed | May 9, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69feb3bd700c8190991ed200cd3c04db |
completed | May 9, 2026, 4:10 a.m. |
Created at: May 1, 2026, 1:52 a.m.