Triple
T37008067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthedain |
E915857
|
entity |
| Predicate | heirTraditionContinuedAs |
P139349
|
FINISHED |
| Object | Chieftains of the Dúnedain |
—
|
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: Chieftains of the Dúnedain | Statement: [Arthedain, heirTraditionContinuedAs, Chieftains of the Dúnedain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heirTraditionContinuedAs Context triple: [Arthedain, heirTraditionContinuedAs, Chieftains of the Dúnedain]
-
A.
continuedTraditionOf
chosen
Indicates that one entity carries on, preserves, or perpetuates a tradition, practice, or custom that originated with another entity.
-
B.
traditionInheritedFrom
Indicates that a tradition has been passed down or derived from an earlier source, group, or culture.
-
C.
usesTradition
Indicates that one entity employs or draws upon a tradition as a guiding method, resource, or influence in its actions or practices.
-
D.
traditionSince
Indicates that a tradition has been continuously practiced or recognized starting from a specified point in time.
-
E.
mainTradition
Indicates that one entity represents the primary or dominant tradition 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_69f76e90ed548190b187d2475f5c807d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.