Triple
T4276074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pyboard |
E97049
|
entity |
| Predicate | documentationAvailableAt |
P28142
|
FINISHED |
| Object | https://docs.micropython.org |
—
|
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://docs.micropython.org | Statement: [pyboard, documentationAvailableAt, https://docs.micropython.org]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentationAvailableAt Context triple: [pyboard, documentationAvailableAt, https://docs.micropython.org]
-
A.
documentationUI
Indicates a relationship where a user interface element is used to present, navigate, or interact with documentation content.
-
B.
documentedUsing
Indicates that something is recorded, described, or specified by means of a particular document, tool, or documentation method.
-
C.
textAvailableAt
Indicates that a specific piece of text can be accessed or obtained at a given location, source, or resource.
-
D.
hasDocumentationAt
chosen
Indicates that something is documented or described in a specific document, file, or location.
-
E.
languageOfDocumentation
Indicates the language in which the documentation for an entity is written or provided.
- 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_69b34544be3c819084d1ab82d29f90c5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3501d677481909e7416a1d2b0008c |
completed | March 12, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69b347faa45481908c19c29fb906dc92 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.