Triple
T35078802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advocates (Scotland) |
E1012375
|
entity |
| Predicate | canAcceptDirectAccessIn |
P54140
|
FINISHED |
| Object | certain circumstances |
—
|
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: certain circumstances | Statement: [Advocates (Scotland), canAcceptDirectAccessIn, certain circumstances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canAcceptDirectAccessIn Context triple: [Advocates (Scotland), canAcceptDirectAccessIn, certain circumstances]
-
A.
mayDirect
Indicates that one entity has the permission or authority to direct, manage, or oversee the actions or operations of another entity.
-
B.
allowsIndividualAccess
Indicates that one entity grants another entity permission to access something on an individual, per-person basis.
-
C.
canAccedeTo
chosen
Indicates that one entity has the ability, permission, or right to gain access to or enter into another entity, resource, or state.
-
D.
supportsCLIAccess
Indicates that one entity enables or allows another entity to access a Command Line Interface (CLI).
-
E.
canPass
Indicates that one entity is able or permitted to move through, cross, or successfully traverse another entity or barrier.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.