Triple
T36391821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legislative Assembly of the Federal District |
E896347
|
entity |
| Predicate | replacedByBodyType |
P53146
|
FINISHED |
| Object | unicameral city congress |
—
|
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: unicameral city congress | Statement: [Legislative Assembly of the Federal District, replacedByBodyType, unicameral city congress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedByBodyType Context triple: [Legislative Assembly of the Federal District, replacedByBodyType, unicameral city congress]
-
A.
replacedBodyType
chosen
Indicates that one body type has been substituted or superseded by another body type.
-
B.
successorBodyStyleChange
Indicates that one body style directly follows and replaces another in a sequence of design or model changes.
-
C.
replacedBody
Indicates that one entity has taken the place of another entity’s body, substituting it in whole or in part.
-
D.
appliesToBodyType
Indicates that something (such as a rule, feature, or specification) is relevant or applicable to a particular body type.
-
E.
bodyTypes
Indicates a relationship where one or more body types are associated with or assigned to an entity.
- 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: May 3, 2026, 4:10 p.m.