Triple
T29202897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tolkien |
E740326
|
entity |
| Predicate | hasRelatedPage |
P16909
|
FINISHED |
| Object | Tolkien family |
—
|
NE NERFINISHED |
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: Tolkien family | Statement: [Tolkien, hasRelatedPage, Tolkien family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelatedPage Context triple: [Tolkien, hasRelatedPage, Tolkien family]
-
A.
hasPage
chosen
Indicates that one entity includes, is associated with, or is documented by a specific page (such as a web page or document page).
-
B.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
-
C.
hasRelatedCategory
Indicates that one category is associated with another category through a non-hierarchical, contextually relevant relationship.
-
D.
hasRelatedPlan
Indicates that one entity is associated with another entity through a plan that is relevant or connected to it.
-
E.
hasRelatedResult
Indicates that one entity has an associated outcome, effect, or result that is meaningfully connected to it.
- 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69ffc3f0b19c8190b5a749bc3cad21dd |
completed | May 9, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69ffc1b882808190932b2d43ea5537c9 |
completed | May 9, 2026, 11:22 p.m. |
Created at: April 28, 2026, 12:07 p.m.