Triple
T27486063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rayburn House Office Building |
E693738
|
entity |
| Predicate | hasUndergroundConnectionTo |
P41500
|
FINISHED |
| Object | United States Capitol |
—
|
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: United States Capitol | Statement: [Rayburn House Office Building, hasUndergroundConnectionTo, United States Capitol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUndergroundConnectionTo Context triple: [Rayburn House Office Building, hasUndergroundConnectionTo, United States Capitol]
-
A.
hasUndergroundConnections
chosen
Indicates that one entity is linked to another through subterranean or hidden passageways, networks, or channels.
-
B.
hasOverpassOrSubway
Indicates that one location is connected to or accessible from another via an overpass or a subway passage.
-
C.
hasSubway
Indicates that a place is served by or contains a subway (metro) system.
-
D.
hasUndergroundSection
Indicates that an entity includes a portion or segment that is located below ground level.
-
E.
hasPublicTransportConnection
Indicates that there is an available public transportation link or service connecting the related entities.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 27, 2026, 1:02 p.m.