Triple
T18169747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chamber of Deputies (Jordan) |
E434992
|
entity |
| Predicate | relationToOtherHouse |
P50894
|
FINISHED |
| Object | lower house |
—
|
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 | Statement: [Chamber of Deputies (Jordan), relationToOtherHouse, lower house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToOtherHouse Context triple: [Chamber of Deputies (Jordan), relationToOtherHouse, lower house]
-
A.
relationshipBetweenHouses
chosen
Indicates a relational connection or association that exists between two or more houses.
-
B.
relationToMLS
Indicates a relationship or association that an entity has with a specific MLS (Multiple Listing Service) system or record.
-
C.
associatedHouse
Indicates a relationship where one entity is linked or connected to a particular house, typically as its related or corresponding house.
-
D.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
E.
relationToTheIndependent
Indicates a relationship in which one entity is connected or relevant to another entity that is designated as independent.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4df555af081908a2f12bce6a13f56 |
completed | April 19, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.