Triple
T36544654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | primary canon (Tolkien legendarium) |
E901107
|
entity |
| Predicate | coreAuthor |
P142885
|
FINISHED |
| Object | J. R. R. Tolkien |
—
|
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: J. R. R. Tolkien | Statement: [primary canon (Tolkien legendarium), coreAuthor, J. R. R. Tolkien]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreAuthor Context triple: [primary canon (Tolkien legendarium), coreAuthor, J. R. R. Tolkien]
-
A.
canonicalAuthor
Indicates that an entity is the officially recognized or standard author of a given work or resource.
-
B.
centralWorkAuthor
chosen
Indicates that an author is the primary creator or main writer responsible for a central or key work.
-
C.
featuresAuthor
Indicates that something includes or highlights a particular author as a primary associated contributor.
-
D.
originAuthor
Indicates that an entity is the original creator or author of another entity (such as a work, document, or idea).
-
E.
authorType
Indicates the specific role or category of authorship associated with an entity, such as primary author, co-author, or editor.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.