Triple
T25510432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan Ramsay |
E639360
|
entity |
| Predicate | earliestRecordedAncestor |
P3891
|
FINISHED |
| Object | Symon de Ramesie |
—
|
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: Symon de Ramesie | Statement: [Clan Ramsay, earliestRecordedAncestor, Symon de Ramesie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestRecordedAncestor Context triple: [Clan Ramsay, earliestRecordedAncestor, Symon de Ramesie]
-
A.
earliestKnownAncestor
chosen
Indicates that one entity is the most distant (oldest) known ancestor in the lineage of another entity.
-
B.
foundingAncestor
Indicates that one entity is the original progenitor or earliest known ancestor from whom another entity or lineage descends.
-
C.
ancestralDomainOf
Indicates that one entity is the original or historically prior domain from which another domain is derived or descended.
-
D.
forefatherOf
Indicates that one person is an ancestor, typically from an earlier generation, of another person.
-
E.
ancestor
Indicates that one entity is a forebear of another in a lineage, occurring in an earlier generation and connected through one or more parent-child relationships.
- 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f809726081908ae4122cd4e581c1 |
completed | May 2, 2026, 1:11 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 2:48 p.m.