Triple
T27582699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dojo Toolkit |
E699620
|
entity |
| Predicate | hasAPIReference |
P122701
|
FINISHED |
| Object | https://dojotoolkit.org/api/ |
—
|
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: https://dojotoolkit.org/api/ | Statement: [Dojo Toolkit, hasAPIReference, https://dojotoolkit.org/api/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAPIReference Context triple: [Dojo Toolkit, hasAPIReference, https://dojotoolkit.org/api/]
-
A.
hasAPIs
Indicates that one entity provides or exposes application programming interfaces (APIs) that can be used or accessed by another entity.
-
B.
documentationReference
Indicates that one entity serves as a documentation source or reference that explains, specifies, or supports another entity.
-
C.
hasOnlineDocumentation
chosen
Indicates that an entity is accompanied by documentation that is available in an online or web-accessible form.
-
D.
includesAPI
Indicates that one entity provides or contains an application programming interface (API) that can be used by another entity.
-
E.
usedInAPIs
Indicates that something is employed or referenced as a component or feature within one or more APIs.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 27, 2026, 2:03 p.m.