Triple
T18319478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darley Arabian |
E438830
|
entity |
| Predicate | bloodlineType |
P82095
|
FINISHED |
| Object | sire line |
—
|
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: sire line | Statement: [Darley Arabian, bloodlineType, sire line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bloodlineType Context triple: [Darley Arabian, bloodlineType, sire line]
-
A.
isLineageType
chosen
Indicates that one entity represents a type or category within the lineage or ancestral line of another entity.
-
B.
lineageSystem
Indicates a hierarchical ancestry or descent relationship that traces how entities are derived from or originate through one another within a system.
-
C.
typeOfAncestry
Indicates that one entity’s ancestry or lineage is characterized as being of a particular type or origin in relation to another entity.
-
D.
bloodType
Indicates that one entity has a specific blood group classification (such as A, B, AB, or O, with a positive or negative Rh factor).
-
E.
heritageLine
Indicates that one entity is a historical or traditional predecessor, lineage, or source from which the other entity derives or continues.
- 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.