Triple
T27470558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longworth House Office Building |
E693304
|
entity |
| Predicate | hasSubBasement |
P187566
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Longworth House Office Building, hasSubBasement, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubBasement Context triple: [Longworth House Office Building, hasSubBasement, true]
-
A.
hasBasement
Indicates that a building or structure includes a basement level as part of its physical layout.
-
B.
hasBasementFeature
Indicates that a property’s basement includes or is characterized by a specific feature or attribute.
-
C.
hasBasementUse
Indicates that a building or structure’s basement is used for a specified purpose or function.
-
D.
hasBasementExposure
Indicates that a property or structure is subject to exposure or adjacency to a basement area, such as having walls or spaces that directly border or open into a basement.
-
E.
hasBasementVenue
Indicates that a venue or space is located in, or functions as, a basement-level area within a building.
- F. None of above. chosen
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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb6fdab95c81909acff3c6a2359787 |
completed | May 6, 2026, 4:44 p.m. |
Created at: April 27, 2026, 12:53 p.m.