Triple
T31056309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASBO |
E791406
|
entity |
| Predicate | typicalRestrictions |
P90727
|
FINISHED |
| Object | prohibition from entering certain areas |
—
|
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: prohibition from entering certain areas | Statement: [ASBO, typicalRestrictions, prohibition from entering certain areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRestrictions Context triple: [ASBO, typicalRestrictions, prohibition from entering certain areas]
-
A.
mayHaveRestriction
chosen
Indicates that an entity can be subject to one or more limitations, conditions, or constraints, though such restrictions are not necessarily present.
-
B.
consumptionRestriction
Indicates a limitation or prohibition on the use or consumption of a specified resource, product, or item.
-
C.
notableRestriction
Indicates that there is a significant limitation, constraint, or prohibition that meaningfully affects the entity or its use.
-
D.
hadRestrictions
Indicates that an entity was subject to specific limitations, rules, or constraints during a given time or context.
-
E.
oftenRestrictedTo
Indicates that the use, occurrence, or applicability of something is frequently limited to a particular subset, context, or condition.
- 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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9 p.m.