Triple
T33747200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stratosphere Tower |
E864729
|
entity |
| Predicate | hasHeightRanking |
P193851
|
FINISHED |
| Object | one of the tallest structures in Las Vegas |
—
|
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: one of the tallest structures in Las Vegas | Statement: [Stratosphere Tower, hasHeightRanking, one of the tallest structures in Las Vegas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeightRanking Context triple: [Stratosphere Tower, hasHeightRanking, one of the tallest structures in Las Vegas]
-
A.
hasRankingStrength
Indicates the relative strength or priority of an entity’s ranking compared to others in a given ordering or evaluation.
-
B.
hasRankingUnit
Indicates that one entity is associated with a specific unit or scale used to express its ranking or ordered position.
-
C.
isHighRanking
Indicates that an entity holds a position of relatively great authority, status, or seniority within a hierarchy or organization.
-
D.
heightRankWithinStructure
Indicates the relative ordering of an entity’s height compared to other entities within the same structure.
-
E.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
| PDg | Predicate description generation | batch_69fd57b9cdec81908536c4159e375931 |
completed | May 8, 2026, 3:25 a.m. |
Created at: May 1, 2026, 1:45 a.m.