Triple
T26472980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Speaker pro tempore |
E665949
|
entity |
| Predicate | foundInBodyType |
P29758
|
FINISHED |
| Object | lower house of a 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: lower house of a legislature | Statement: [Speaker pro tempore, foundInBodyType, lower house of a legislature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundInBodyType Context triple: [Speaker pro tempore, foundInBodyType, lower house of a legislature]
-
A.
presentInBodyType
chosen
Indicates that something exists or occurs within a specific type or category of body.
-
B.
discoveredOnBodyBy
Indicates that a body was discovered by a particular person or agent.
-
C.
residesOverBodyType
Indicates that one entity is positioned or located above another entity that is characterized by a specific body type.
-
D.
discoveredOnBody
Indicates that something (such as an item, mark, or substance) was found on the surface or person of a body.
-
E.
bodyFound
Indicates that the location or circumstance where a body was discovered has been identified or recorded.
- 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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 12:21 a.m.