Triple
T1735185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wikibooks |
E37904
|
entity |
| Predicate | mainPage |
P21673
|
FINISHED |
| Object | https://www.wikibooks.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://www.wikibooks.org/ | Statement: [Wikibooks, mainPage, https://www.wikibooks.org/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainPage Context triple: [Wikibooks, mainPage, https://www.wikibooks.org/]
-
A.
mainIndex
Indicates that one entity serves as the primary or central index or reference point for another entity within a structured system.
-
B.
webPage
chosen
Indicates that one entity is a web page associated with, describing, or providing information about another entity.
-
C.
homeSection
Indicates that something belongs to, is part of, or is designated as the primary/home section within a larger structure or collection.
-
D.
mainFunctions
Indicates that the subject serves as the primary or central functional component or role for the object.
-
E.
mainEntranceOn
Indicates that the primary entrance of one entity is located on or faces toward another entity, such as a particular side, street, or boundary.
- 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.