Triple
T37378405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paths of the Dead |
E928358
|
entity |
| Predicate | relatedToKingdom |
P20193
|
FINISHED |
| Object | Gondor |
E261160
|
NE 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: Gondor | Statement: [Paths of the Dead, relatedToKingdom, Gondor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToKingdom Context triple: [Paths of the Dead, relatedToKingdom, Gondor]
-
A.
kingdomAssociatedWith
chosen
Indicates a relationship where something is connected or related to a particular kingdom, such as belonging to, originating from, or being governed by that kingdom.
-
B.
mentionsKingdom
Indicates that one entity explicitly refers to or brings up the topic of a kingdom in relation to another entity.
-
C.
kingdomDomain
Indicates that a kingdom is part of, or belongs within, a particular higher-level domain.
-
D.
recognizedAsKingdom
Indicates that an entity is formally acknowledged or classified as a kingdom within a given system or context.
-
E.
kingdomsIncluded
Indicates that one or more kingdoms are contained within, or form part of, a larger political or territorial entity.
- F. None of above.
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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4076eb496c8190870c2b639826b934 |
completed | June 28, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.