Triple
T21365433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pennsylvania Route 28 |
E526896
|
entity |
| Predicate | hasLimitedAccessSections |
P63696
|
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: [Pennsylvania Route 28, hasLimitedAccessSections, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLimitedAccessSections Context triple: [Pennsylvania Route 28, hasLimitedAccessSections, yes]
-
A.
accessRestrictedTo
Indicates that access to a resource, location, or information is limited exclusively to a specified entity or group under defined conditions.
-
B.
hasPublicAccessRestrictions
chosen
Indicates that there are specific limitations or conditions governing public access to the associated resource or entity.
-
C.
hasAccessConstraint
Indicates that there is a limiting condition or rule governing the ability to access or use a particular resource, service, or action.
-
D.
hasLimitedAuthorityOver
Indicates that one entity holds a constrained or partial power to direct, control, or make decisions about another entity, but not full or unrestricted authority.
-
E.
hasLimitedServiceType
Indicates that an entity is associated with a service that is restricted in scope, availability, or functionality compared to full or standard service types.
- 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_69e0b51d8a308190b09113b3b3f9bc15 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b06ec4208190b9ed3484afd85852 |
completed | April 22, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:09 p.m.