Triple
T10685919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osage language |
E251875
|
entity |
| Predicate | hasOnlineResources |
P73430
|
FINISHED |
| Object | online dictionaries |
—
|
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: online dictionaries | Statement: [Osage language, hasOnlineResources, online dictionaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnlineResources Context triple: [Osage language, hasOnlineResources, online dictionaries]
-
A.
hasOnlineResourceType
chosen
Indicates that an entity’s associated online resource belongs to a specific type or category (e.g., webpage, dataset, video).
-
B.
hasOnlineTools
Indicates that an entity provides or includes tools or functionalities that are accessible via the internet.
-
C.
hasOnlinePlatform
Indicates that an entity operates, maintains, or is associated with a presence or service on an online platform.
-
D.
hasOnlineDatabases
Indicates that an entity maintains or provides access to one or more databases that are available online.
-
E.
supportsOnlineContent
Indicates that one entity provides the infrastructure, functionality, or capability for another entity to host, deliver, or interact with content over the internet.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd182d7c819099ff6ffb3a7083f5 |
completed | April 9, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8cc0788190b4c02a772e4b58b3 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:10 p.m.