Triple
T33112006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arathorn II |
E847353
|
entity |
| Predicate | ancestralRealm |
P150822
|
FINISHED |
| Object | Arnor |
—
|
NE NERFINISHED |
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: Arnor | Statement: [Arathorn II, ancestralRealm, Arnor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ancestralRealm Context triple: [Arathorn II, ancestralRealm, Arnor]
-
A.
ancestralDomain
chosen
Indicates that one entity is the traditional or long-held territory or domain from which another entity originates or to which it is ancestrally connected.
-
B.
ancestralGroup
Indicates that one entity is a broader ancestral lineage, population, or group from which the other entity descends or originates.
-
C.
ancestralDomainOf
Indicates that one entity is the original or historically prior domain from which another domain is derived or descended.
-
D.
ancestorHouse
Indicates that one entity is the house or dwelling associated with the ancestors of another entity.
-
E.
birthRealm
Indicates the realm, world, or plane in which an entity was born.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:27 a.m.