Triple
T4415706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Assembly of São Tomé and Príncipe |
E94965
|
entity |
| Predicate | currentBuildingFunction |
P16394
|
FINISHED |
| Object | seat of the legislature |
—
|
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: seat of the legislature | Statement: [National Assembly of São Tomé and Príncipe, currentBuildingFunction, seat of the legislature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentBuildingFunction Context triple: [National Assembly of São Tomé and Príncipe, currentBuildingFunction, seat of the legislature]
-
A.
currentBuilding
Indicates that an entity is located in, associated with, or belongs to the building that is relevant in the current context.
-
B.
hasBuildingFunction
chosen
Indicates that a building is used for or serves a particular function or purpose.
-
C.
buildingCurrentName
Indicates the name currently used to refer to a given building.
-
D.
openedAsCurrentBuilding
Indicates that an entity began operating or was inaugurated in its current building or physical premises.
-
E.
currentFunction
Indicates that an entity is presently serving in a specific role, position, or capacity.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b354eabb2481908ad10d21e1379e7f |
completed | March 13, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69b34f5d0c54819085c08533bb58030a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:29 p.m.