Triple
T32518998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSG |
E831131
|
entity |
| Predicate | oppositeHouse |
P39169
|
FINISHED |
| Object | Contracted Parties House |
—
|
NE NERFINISHED |
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: Contracted Parties House | Statement: [CSG, oppositeHouse, Contracted Parties House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oppositeHouse Context triple: [CSG, oppositeHouse, Contracted Parties House]
-
A.
opposite
Indicates that one entity is positioned or oriented directly across from, or in a contrary or reverse relation to, another entity.
-
B.
oppositeFacility
Indicates that one facility is located directly across from or facing another facility.
-
C.
oppositeOffice
Indicates that one office is located directly opposite another office, typically facing each other across a corridor or space.
-
D.
oppositeChamber
chosen
Indicates that two legislative bodies or chambers are counterparts within the same bicameral system, each serving as the other’s opposite house.
-
E.
opposingLocation
Indicates that two entities are located directly opposite each other, typically across a defined reference such as a street, corridor, or boundary.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 1, 2026, 1 a.m.