Triple
T18319488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darley Arabian |
E438830
|
entity |
| Predicate | bloodlineContribution |
P115355
|
FINISHED |
| Object | Arabian ancestry in Thoroughbreds |
—
|
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: Arabian ancestry in Thoroughbreds | Statement: [Darley Arabian, bloodlineContribution, Arabian ancestry in Thoroughbreds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bloodlineContribution Context triple: [Darley Arabian, bloodlineContribution, Arabian ancestry in Thoroughbreds]
-
A.
genealogicalLine
Indicates a genealogical relationship connecting individuals through lines of descent or ancestry.
-
B.
heritageLine
Indicates that one entity is a historical or traditional predecessor, lineage, or source from which the other entity derives or continues.
-
C.
sharesFamilyLineageWith
Indicates that two entities descend from the same family line or share common ancestors.
-
D.
lineageRelatedTo
Indicates a relationship where two entities are connected through a line of descent or ancestry within the same lineage.
-
E.
sourceOfLineageFor
chosen
Indicates that one entity serves as the origin or ancestral source from which another entity’s lineage is derived.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aa4d3308190883714e1ef6a1d84 |
completed | April 19, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.