Triple
T28860109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Texas Giant |
E728835
|
entity |
| Predicate | hasRiderHeightRestriction |
P8078
|
FINISHED |
| Object | 48 in |
—
|
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: 48 in | Statement: [New Texas Giant, hasRiderHeightRestriction, 48 in]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiderHeightRestriction Context triple: [New Texas Giant, hasRiderHeightRestriction, 48 in]
-
A.
heightRestriction
chosen
Indicates that there is a limit or constraint on how tall an entity is allowed or required to be in a given context.
-
B.
heightRestrictionWithCompanion
Indicates that there is a height-based restriction which may be satisfied or modified when the person is accompanied by a qualifying companion.
-
C.
rideHeight
Indicates the vertical distance between a vehicle’s chassis and the ground, defining how high it sits relative to the surface.
-
D.
rideRestriction
Indicates that there is a limitation or rule governing whether, how, or under what conditions one entity may ride or be transported by another.
-
E.
hasClimbingRestriction
Indicates that there is a rule, limitation, or prohibition affecting whether and how climbing is allowed on the associated object or location.
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 28, 2026, 6:46 a.m.