Triple
T11049336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cracks of Doom |
E261205
|
entity |
| Predicate | primaryFunctionInLore |
P97516
|
FINISHED |
| Object | place where the One Ring can be unmade |
—
|
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: place where the One Ring can be unmade | Statement: [Cracks of Doom, primaryFunctionInLore, place where the One Ring can be unmade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFunctionInLore Context triple: [Cracks of Doom, primaryFunctionInLore, place where the One Ring can be unmade]
-
A.
primaryFunctionInAntiquity
Indicates the main role or purpose an entity served during ancient times.
-
B.
primaryFunctionInSeries
Indicates that an entity serves as the main or most important function within a particular series or sequence.
-
C.
primaryFunctionInPractice
Indicates that an entity serves as the main or most important function or role within a given practical context or real-world usage.
-
D.
primaryCharacteristics
Indicates the main defining traits or features that most fundamentally characterize an entity.
-
E.
primaryFunctionInPrehistory
Indicates the main role or use an entity had during prehistoric times, before written records.
- F. None of above. chosen
Provenance (4 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79867fa28819094f564273e3ef51d |
completed | April 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:26 p.m.