Triple
T18244901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palace Malice |
E436923
|
entity |
| Predicate | hasSireLine |
P115355
|
FINISHED |
| Object | Mr. Prospector sire line via Smart Strike |
—
|
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: Mr. Prospector sire line via Smart Strike | Statement: [Palace Malice, hasSireLine, Mr. Prospector sire line via Smart Strike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSireLine Context triple: [Palace Malice, hasSireLine, Mr. Prospector sire line via Smart Strike]
-
A.
sireOf
Indicates that one entity is the male parent (father) of another entity.
-
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.
damsire
Indicates that one entity is the maternal grandfather (sire of the dam) of another, typically in an animal’s pedigree.
-
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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f7e5d63081908d0e6249578867a1 |
completed | April 19, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:33 a.m.