Triple
T36611652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Angband |
E903479
|
entity |
| Predicate | inspiredTitleFor |
P21192
|
FINISHED |
| Object | Sauron as Dark Lord |
—
|
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: Sauron as Dark Lord | Statement: [King of Angband, inspiredTitleFor, Sauron as Dark Lord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredTitleFor Context triple: [King of Angband, inspiredTitleFor, Sauron as Dark Lord]
-
A.
inspiredTitle
chosen
Indicates that one title was created under the influence or inspiration of another title.
-
B.
inspiredLatinTitleOf
Indicates that one entity served as the creative or conceptual inspiration for the Latin title of another entity.
-
C.
createdTitleBy
Indicates that a title (such as a work, document, or creative piece) was created by a specific agent or creator.
-
D.
decidesTitleOf
Indicates that one entity has the authority or role to determine and assign the title of another entity.
-
E.
titleCreation
Indicates that an entity is responsible for creating, originating, or authoring the title associated with 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_69f76e6960e4819092047756ceb9a17e |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: May 3, 2026, 4:11 p.m.