Triple
T7881886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iclingas |
E182997
|
entity |
| Predicate | hasAncestralClaim |
P30356
|
FINISHED |
| Object | descent from Icel son of Eomer |
—
|
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: descent from Icel son of Eomer | Statement: [Iclingas, hasAncestralClaim, descent from Icel son of Eomer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncestralClaim Context triple: [Iclingas, hasAncestralClaim, descent from Icel son of Eomer]
-
A.
hasAncestralRoots
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
-
B.
hasClaimOn
Indicates that one entity holds a right, entitlement, or demand over another entity or its resources.
-
C.
claimedDescentFrom
chosen
Indicates that one entity asserts or maintains that it is descended from, or originates genealogically from, another entity.
-
D.
lineageClaim
Indicates a claim or assertion that one entity is descended from, or belongs to the ancestral line of, another entity.
-
E.
hasMatrilinealConnection
Indicates a relationship where one entity is connected to another through a line of descent traced exclusively through female ancestors.
- 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_69ca828af6e48190a06ee7010d8f0e64 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39c14a188190a225ca3c7e515b0c |
completed | March 31, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69cae92b0cd881908e715a10d3252e83 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:58 p.m.