Triple
T15818418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voyageur II |
E383537
|
entity |
| Predicate | accessProvidesTo |
P51771
|
FINISHED |
| Object | remote Windigo area of Isle Royale |
—
|
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: remote Windigo area of Isle Royale | Statement: [Voyageur II, accessProvidesTo, remote Windigo area of Isle Royale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessProvidesTo Context triple: [Voyageur II, accessProvidesTo, remote Windigo area of Isle Royale]
-
A.
accessProvides
chosen
Indicates that one entity grants or enables the ability to use, enter, or retrieve another entity or resource.
-
B.
accessIs
Indicates that one entity has the ability, permission, or means to reach, use, or interact with another entity or resource.
-
C.
accessDeterminedBy
Indicates that the ability to access a resource is governed or controlled by a specified condition, rule, or authority.
-
D.
accessRole
Indicates the specific permissions or level of authority an entity has when accessing another entity or resource.
-
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.
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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a552008190863343c9d41ebf3f |
completed | April 16, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.