Triple
T27560666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows Address Book |
E695760
|
entity |
| Predicate | canBeAccessedProgrammaticallyVia |
P28414
|
FINISHED |
| Object | WAB API |
—
|
NE NERFINISHED |
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: WAB API | Statement: [Windows Address Book, canBeAccessedProgrammaticallyVia, WAB API]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeAccessedProgrammaticallyVia Context triple: [Windows Address Book, canBeAccessedProgrammaticallyVia, WAB API]
-
A.
accessibleOn
chosen
Indicates that one entity can be reached, used, or obtained through another entity (such as a platform, device, or medium).
-
B.
accessibleAs
Indicates that one entity can be reached, used, or obtained through another entity, often as an alternative form, route, or representation.
-
C.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
D.
hasAccessibleAccess
Indicates that an entity provides a form of access that is usable and reachable under defined accessibility conditions or standards.
-
E.
canBeControlledFrom
Indicates that one entity has the ability or authority to operate, direct, or manage another entity remotely or indirectly.
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 27, 2026, 1:39 p.m.