Triple
T7022250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR-143 |
E162854
|
entity |
| Predicate | hasLimitedAccess |
P8521
|
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: [SR-143, hasLimitedAccess, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLimitedAccess Context triple: [SR-143, hasLimitedAccess, yes]
-
A.
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.
-
B.
hasHumanAccess
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
-
C.
accessRestrictedTo
chosen
Indicates that access to a resource, location, or information is limited exclusively to a specified entity or group under defined conditions.
-
D.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
E.
hasDisabledAccess
Indicates that an entity provides facilities, features, or accommodations that make it accessible to people with disabilities.
- 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_69c6885b26248190a857541e3d10e299 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e5ecd4488190bf19e42de55da98b |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b8118481909d76eb6616160e80 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:35 p.m.