Triple
T7817129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DF |
E181037
|
entity |
| Predicate | associatedCapitalStatus |
P44004
|
FINISHED |
| Object | national capital region of Brazil |
—
|
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: national capital region of Brazil | Statement: [DF, associatedCapitalStatus, national capital region of Brazil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCapitalStatus Context triple: [DF, associatedCapitalStatus, national capital region of Brazil]
-
A.
hasAssociatedCapital
chosen
Indicates that an entity is linked to a specific capital city that serves as its primary administrative or political center.
-
B.
sharesCapitalStatusWith
Indicates that two entities have the same capital-related status, such as both being capitals or both not being capitals.
-
C.
associatedStatus
Indicates that one entity is linked to or characterized by a particular status or condition.
-
D.
earlierCapitalAssociated
Indicates that one entity served as a capital city at an earlier time than the other associated capital entity.
-
E.
capitalStatusStart
Indicates the point in time when a place first acquires its status as a capital.
- 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_69ca828153f48190bdb27ac46f8e0745 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf96ea6d881908eff5f750e0f6700 |
completed | March 30, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69cae91687788190af9cb7aaa996d291 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:39 p.m.