Triple
T437526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capitol Visitor Center |
E10042
|
entity |
| Predicate | depthBelowGround |
P3822
|
FINISHED |
| Object | approximately 3 to 4 stories |
—
|
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: approximately 3 to 4 stories | Statement: [Capitol Visitor Center, depthBelowGround, approximately 3 to 4 stories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depthBelowGround Context triple: [Capitol Visitor Center, depthBelowGround, approximately 3 to 4 stories]
-
A.
ground
Indicates that one entity is in contact with or supported by the ground or a ground-like surface.
-
B.
depth
chosen
Indicates the vertical distance from a reference surface or top point down to a lower point or bottom within a medium or space.
-
C.
partlyBelowSeaLevel
Indicates that an entity’s elevation is such that some, but not all, of it lies below sea level.
-
D.
oceanDepthBelow
Indicates that one location or point in the ocean is situated at a greater depth (deeper below the surface) than another.
-
E.
existsBelow
Indicates that at least one instance of an entity is located or occurs at a lower level or position relative to another entity.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef26bb78819089b3b5dac0330619 |
completed | Feb. 28, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69a2eddb98e081909efcf9f0a955a908 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.