Triple
T7460247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roar |
E176226
|
entity |
| Predicate | riderRestriction |
P31973
|
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: [Roar, riderRestriction, 48 in]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riderRestriction Context triple: [Roar, riderRestriction, 48 in]
-
A.
transportRestriction
Indicates that there are limitations, prohibitions, or special conditions governing the use of a particular mode or means of transportation between entities.
-
B.
rideLimit
chosen
Indicates a constraint on the maximum number, duration, or frequency of rides permitted for an entity.
-
C.
hasLimitedRoadAccess
Indicates that an entity can only be reached by a small number of roads, restricted routes, or otherwise constrained vehicular access.
-
D.
supportsRiderCategory
Indicates that one entity is capable of accommodating, enabling, or being compatible with a specified rider category.
-
E.
requiredRiderOath
Indicates that an individual is obligated to take or uphold a specific rider’s oath as a condition for participation or status.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d525708190b7838e07ac2fbe1f |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:38 p.m.