Triple
T29607812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arviragus |
E754624
|
entity |
| Predicate | hiddenLineage |
P167504
|
FINISHED |
| Object | son of King Cymbeline |
—
|
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: son of King Cymbeline | Statement: [Arviragus, hiddenLineage, son of King Cymbeline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hiddenLineage Context triple: [Arviragus, hiddenLineage, son of King Cymbeline]
-
A.
heritageLine
Indicates that one entity is a historical or traditional predecessor, lineage, or source from which the other entity derives or continues.
-
B.
hasNotableLineageFor
Indicates that one entity possesses a distinguished or noteworthy ancestry, heritage, or lineage in relation to another entity.
-
C.
hasNotableLineage
Indicates that an entity descends from, or is associated with, a distinguished or historically significant family, ancestry, or heritage.
-
D.
lineageClaim
Indicates a claim or assertion that one entity is descended from, or belongs to the ancestral line of, another entity.
-
E.
hasLineageDocumentedIn
Indicates that the lineage or ancestry of an entity is recorded or evidenced in a specified document or source.
- F. None of above. chosen
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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66de8aaf48190a2bc6177604a3771 |
completed | May 2, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 6:26 p.m.