Triple
T93692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States House of Representatives |
E1882
|
entity |
| Predicate | buildingSection |
P4394
|
FINISHED |
| Object | House wing of the United States Capitol |
—
|
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: House wing of the United States Capitol | Statement: [United States House of Representatives, buildingSection, House wing of the United States Capitol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingSection Context triple: [United States House of Representatives, buildingSection, House wing of the United States Capitol]
-
A.
building
Indicates that one entity constructs, assembles, or develops another entity, typically over a period of time.
-
B.
buildingType
Indicates the specific category or function that characterizes what kind of building something is.
-
C.
constructionMethod
Indicates the technique or process by which something is built, assembled, or created.
-
D.
builder
Indicates that an entity is responsible for constructing, creating, or assembling another entity.
-
E.
usesBuilding
Indicates that one entity makes use of, occupies, or operates within a particular 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_69a24d1a97dc819094e6c021fe9b05a7 |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a2512ef600819084d3c627f0d534f4 |
completed | Feb. 28, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69a24eb9a5ac8190b1d1300e8c4e3606 |
completed | Feb. 28, 2026, 2:11 a.m. |
| PDg | Predicate description generation | batch_69a2512cc3108190aefe5e624312f7d0 |
completed | Feb. 28, 2026, 2:21 a.m. |
Created at: Feb. 28, 2026, 2:07 a.m.