Triple
T32496843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryan family |
E830547
|
entity |
| Predicate | hasAncestralDescent |
P154791
|
FINISHED |
| Object | O'Ryan surname bearers |
—
|
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: O'Ryan surname bearers | Statement: [Ryan family, hasAncestralDescent, O'Ryan surname bearers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncestralDescent Context triple: [Ryan family, hasAncestralDescent, O'Ryan surname bearers]
-
A.
hasTribalAncestor
Indicates that an entity is descended from, or has lineage tracing back to, a specified tribal ancestor.
-
B.
hasAncestralRoots
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
-
C.
alsoHasAncestry
Indicates that an entity possesses an additional ancestral lineage or heritage beyond its primary recorded ancestry.
-
D.
hasAncestralFamilyName
Indicates that an entity bears or is associated with a family name inherited from its ancestors.
-
E.
hasTypeOfDescent
chosen
Indicates that one entity possesses a particular kind or category of ancestral or lineage-based origin in relation to 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 1, 2026, 12:59 a.m.