Triple
T33028130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XEP-0060: Publish-Subscribe |
E845094
|
entity |
| Predicate | definesAccessModel |
P93561
|
FINISHED |
| Object | open |
—
|
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: open | Statement: [XEP-0060: Publish-Subscribe, definesAccessModel, open]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesAccessModel Context triple: [XEP-0060: Publish-Subscribe, definesAccessModel, open]
-
A.
hasAccessModel
Indicates that one entity is permitted to use, interact with, or retrieve a particular model controlled by another entity or system.
-
B.
supportsAccessModel
chosen
Indicates that one entity enables, permits, or is compatible with a particular access model used by another entity.
-
C.
usesAccessControlModel
Indicates that one entity employs or implements a specific access control model to govern permissions or regulate access to resources.
-
D.
definedInModel
Indicates that an element or concept is specified, structured, or formally represented within a particular model.
-
E.
hadUserAccessModel
Indicates that a user previously had permission to access or use a specific model.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
Created at: May 1, 2026, 1:23 a.m.