Triple
T28834210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qaryut |
E728132
|
entity |
| Predicate | hasRoadblockOrRestriction |
P153605
|
FINISHED |
| Object | subject to movement restrictions |
—
|
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: subject to movement restrictions | Statement: [Qaryut, hasRoadblockOrRestriction, subject to movement restrictions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadblockOrRestriction Context triple: [Qaryut, hasRoadblockOrRestriction, subject to movement restrictions]
-
A.
hasSpeedRestriction
Indicates that an entity is subject to a specified limit on its allowable speed.
-
B.
hasCarriagewayRestrictions
Indicates that certain limitations or prohibitions apply to the use or access of a specific carriageway.
-
C.
hasLimitedRoadAccess
Indicates that an entity can only be reached by a small number of roads, restricted routes, or otherwise constrained vehicular access.
-
D.
hasSpeedRestrictionReason
Indicates the reason or cause for which a speed restriction has been imposed on an entity.
-
E.
hasObstructions
chosen
Indicates that one entity is blocking, hindering, or limiting another entity’s movement, function, or access.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 28, 2026, 6:38 a.m.