Triple
T504260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Via do Infante |
E10466
|
entity |
| Predicate | hasAccessControl |
P9584
|
FINISHED |
| Object | controlled-access motorway |
—
|
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: controlled-access motorway | Statement: [Via do Infante, hasAccessControl, controlled-access motorway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessControl Context triple: [Via do Infante, hasAccessControl, controlled-access motorway]
-
A.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
B.
hasAccessMode
Indicates the type or method of access that one entity is permitted to use with respect to another entity or resource.
-
C.
hasAccessException
Indicates that a usual access rule or restriction is overridden or exempted for a particular entity or situation.
-
D.
hasChangeControl
Indicates that an entity is subject to a defined process for reviewing, approving, and managing modifications or updates.
-
E.
accessRestriction
chosen
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
- 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f149bd1c81908ff58ac504ace2bf |
completed | Feb. 28, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69a2edfce7a08190a408bc019de60d5d |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.