Triple
T20767216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Effingham, Illinois |
E511128
|
entity |
| Predicate | hasNotableStructureHeight |
P9788
|
FINISHED |
| Object | approximately 198 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: approximately 198 feet | Statement: [Effingham, Illinois, hasNotableStructureHeight, approximately 198 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableStructureHeight Context triple: [Effingham, Illinois, hasNotableStructureHeight, approximately 198 feet]
-
A.
hasSignificantHeight
Indicates that one entity’s height is notably large or substantial relative to a given standard or to other entities.
-
B.
hasHeight
chosen
Indicates that one entity possesses a specific vertical measurement or stature.
-
C.
hasNotableStructureOn
Indicates that a subject entity possesses or features a significant or noteworthy structure located on it.
-
D.
structureHeight
Indicates that a structure has a specific vertical measurement or height.
-
E.
hasTowerHeight
Indicates that an entity (such as a tower or structure) has a specific height value associated with it.
- 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_69e0b4ca01148190ac018e57e0cab46f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c24df58c8190b37398353ce4bf24 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:36 p.m.