Triple
T38459228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wells Fargo Plaza |
E912402
|
entity |
| Predicate | rankInTexasByHeight |
P191125
|
FINISHED |
| Object | second-tallest building in Texas |
—
|
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: second-tallest building in Texas | Statement: [Wells Fargo Plaza, rankInTexasByHeight, second-tallest building in Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankInTexasByHeight Context triple: [Wells Fargo Plaza, rankInTexasByHeight, second-tallest building in Texas]
-
A.
rankAmongTallestInUS
Indicates that the entity is among the tallest of its kind within the United States.
-
B.
populationRankInTexas
Indicates the relative position of an entity in terms of population size compared to other entities within Texas.
-
C.
rankingInStateByHeight
chosen
Indicates the position an entity holds in an ordered list of entities within a specific state, based on their relative height.
-
D.
tallestIn
Indicates that one entity has a greater height than all other relevant entities within a specified group or context.
-
E.
heldRankInTexas
Indicates that a person held a specific official rank, title, or position within the state of Texas.
- 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_69f76e84e2dc81908badf05b3aafa9ea |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 3, 2026, 4:31 p.m.