Triple
T37639799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Session Hall |
E936583
|
entity |
| Predicate | primaryChamberOf |
P11037
|
FINISHED |
| Object | National Legislature Complex |
E275367
|
NE 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 Legislature Complex | Statement: [Main Session Hall, primaryChamberOf, National Legislature Complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryChamberOf Context triple: [Main Session Hall, primaryChamberOf, National Legislature Complex]
-
A.
chamberOf
chosen
Indicates that one entity is a chamber, room, or enclosed space that is part of, contained within, or assigned to another entity.
-
B.
currentRepresentativeChamber
Indicates that an entity currently serves as a representative in a specific legislative chamber.
-
C.
upperLegislativeChamber
Indicates that one entity functions as the upper legislative chamber in the bicameral legislature of the other entity.
-
D.
electedChamber
Indicates that an individual has been chosen through an election to serve as a member of a specific legislative chamber.
-
E.
chamberOfCongress
Indicates that a legislative chamber is a constituent part or house of a specific congress or legislative body.
- F. None of above.
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_69f76ed31d8881908405da6c6d2f0463 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40ba4c0e2081908c326703c5ed4cc1 |
completed | June 28, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.