Triple
T26236404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfursan Silver |
E656183
|
entity |
| Predicate | accessRight |
P166144
|
FINISHED |
| Object | dedicated Alfursan service channels |
—
|
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: dedicated Alfursan service channels | Statement: [Alfursan Silver, accessRight, dedicated Alfursan service channels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessRight Context triple: [Alfursan Silver, accessRight, dedicated Alfursan service channels]
-
A.
accessIs
Indicates that one entity has the ability, permission, or means to reach, use, or interact with another entity or resource.
-
B.
accessRole
Indicates the specific permissions or level of authority an entity has when accessing another entity or resource.
-
C.
accessRestriction
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
-
D.
accessStatus
Indicates the current level or state of permission or availability for accessing a resource or entity.
-
E.
accessFeature
Indicates that one entity is permitted to use or interact with a specific feature or capability of another entity.
- F. None of above. chosen
Provenance (4 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 26, 2026, 9:01 p.m.