Triple
T8532229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christine Falls |
E201979
|
entity |
| Predicate | hasLowerTierHeight |
P53990
|
FINISHED |
| Object | about 37 feet |
—
|
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: about 37 feet | Statement: [Christine Falls, hasLowerTierHeight, about 37 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLowerTierHeight Context triple: [Christine Falls, hasLowerTierHeight, about 37 feet]
-
A.
lowerTierHeight
chosen
Indicates the vertical measurement or elevation of the lower tier in a multi-level structure relative to a reference level.
-
B.
hasLowerTier
Indicates that one entity is ranked, valued, or classified at a lower level or tier relative to another entity.
-
C.
upperTierHeight
Indicates the vertical measurement or elevation of an upper tier relative to a reference level or structure.
-
D.
hasUpperTier
Indicates that one entity occupies a higher or superior level, rank, or layer in a hierarchical structure relative to another entity.
-
E.
hasLowerFloor
Indicates that one location, structure, or level includes or is directly connected to a floor situated below another floor.
- 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_69ca832355b08190b8b6a4ab4a4a3554 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe676e2ac8190b65a3d2a935776fd |
completed | March 31, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:17 p.m.