Triple
T34954631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | l3kernel |
E1008093
|
entity |
| Predicate | documentationProvidedAs |
P128902
|
FINISHED |
| Object | expl3 interface documentation |
—
|
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: expl3 interface documentation | Statement: [l3kernel, documentationProvidedAs, expl3 interface documentation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentationProvidedAs Context triple: [l3kernel, documentationProvidedAs, expl3 interface documentation]
-
A.
documentationProvidedAt
Indicates that documentation is supplied, made available, or presented at a specific time, place, or context.
-
B.
documentationShownIn
chosen
Indicates that certain documentation is displayed or made visible within a particular context, interface, or location.
-
C.
documentationUI
Indicates a relationship where a user interface element is used to present, navigate, or interact with documentation content.
-
D.
providedInformationOn
Indicates that one entity supplied or communicated specific information or details to another entity.
-
E.
documentedUsing
Indicates that something is recorded, described, or specified by means of a particular document, tool, or documentation method.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4 p.m.