Triple
T33123201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tolkien Estate |
E847655
|
entity |
| Predicate | overseesUseOf |
P3020
|
FINISHED |
| Object | J. R. R. Tolkien’s literary works |
—
|
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: J. R. R. Tolkien’s literary works | Statement: [Tolkien Estate, overseesUseOf, J. R. R. Tolkien’s literary works]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overseesUseOf Context triple: [Tolkien Estate, overseesUseOf, J. R. R. Tolkien’s literary works]
-
A.
supervisoryUse
Indicates that one entity exercises oversight, guidance, or monitoring authority over the actions or performance of another entity.
-
B.
oversee
Indicates having responsibility for supervising, directing, or managing the actions or work of another entity.
-
C.
regulatesUse
chosen
Indicates that one entity controls, governs, or sets rules for how another entity may be used.
-
D.
oversawPolicy
Indicates that one entity had supervisory or managerial responsibility for the creation, implementation, or maintenance of a policy affecting another entity or domain.
-
E.
overseesProcedure
Indicates that one entity is responsible for supervising, managing, or directing the execution of a specific procedure performed by another entity.
- 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: May 1, 2026, 1:27 a.m.