Triple
T1735184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wikibooks |
E37904
|
entity |
| Predicate | usesMarkupLanguage |
P2177
|
FINISHED |
| Object | wikitext |
—
|
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: wikitext | Statement: [Wikibooks, usesMarkupLanguage, wikitext]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMarkupLanguage Context triple: [Wikibooks, usesMarkupLanguage, wikitext]
-
A.
usesStandard
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
-
B.
hasLanguageRepresentation
Indicates that an entity is expressed, encoded, or represented using a particular natural or formal language.
-
C.
hasLanguageOn
Indicates that an entity uses or is associated with a particular language in a specific context, medium, or location.
-
D.
usesAttribute
Indicates that one entity employs, relies on, or makes use of a specific attribute of another entity in performing an action or defining a relationship.
-
E.
includesLanguage
chosen
Indicates that one entity contains, supports, or makes use of a specified language as part of its content, functionality, or representation.
- 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_69a8861cc6ac8190ac0b2e31ccf62851 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab5c553e508190b0f511b05e07fa20 |
completed | March 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69aa61c25a648190892de94c997fb983 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.