Triple
T23325108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockefeller Center Christmas Tree |
E591267
|
entity |
| Predicate | typicalHeightRangeMeters |
P149632
|
FINISHED |
| Object | 21–30 meters |
—
|
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: 21–30 meters | Statement: [Rockefeller Center Christmas Tree, typicalHeightRangeMeters, 21–30 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHeightRangeMeters Context triple: [Rockefeller Center Christmas Tree, typicalHeightRangeMeters, 21–30 meters]
-
A.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
-
B.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
C.
averageHeightRange
chosen
Indicates the typical minimum and maximum height values that characterize the usual height span associated with an entity or group.
-
D.
altitudeRange_m
Indicates the range of altitudes, measured in meters, over which the relationship or condition holds.
-
E.
typicalElevationRange
Indicates the usual range of elevation values within which something commonly occurs or exists.
- 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_69e25d1effe4819096907f95f610dbff |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19787ee90819083416193efaab20f |
completed | April 29, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:08 p.m.