Triple
T11143220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A4 motorway |
E263606
|
entity |
| Predicate | isControlledAccess |
P5650
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [A4 motorway, isControlledAccess, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isControlledAccess Context triple: [A4 motorway, isControlledAccess, yes]
-
A.
controlsAccessTo
Indicates that one entity regulates, manages, or determines the ability of another entity to reach, use, or interact with a resource, location, or service.
-
B.
isUnderControlOf
Indicates that one entity is subject to the authority, direction, or governance of another entity.
-
C.
hasInstitutionalControl
Indicates that one entity exercises formal authority, governance, or decision-making power over an institution or organizational body.
-
D.
hasEntranceControl
chosen
Indicates that an entity implements or is subject to mechanisms that regulate or control access to its entrance.
-
E.
circulationControlledBy
Indicates that the flow or movement of something (such as fluids, air, or information) is regulated, directed, or governed by a specified controlling entity.
- 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_69d6aa9c0ba08190bbd19c217489b755 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8623158819096ad1678fa9e72bb |
completed | April 9, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69d75ce104908190b6cc31ef2f67846a |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.