Triple
T18038539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Prospector |
E431576
|
entity |
| Predicate | leadingSireTitle |
P129554
|
FINISHED |
| Object | North America leading sire 1987 |
—
|
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: North America leading sire 1987 | Statement: [Mr. Prospector, leadingSireTitle, North America leading sire 1987]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadingSireTitle Context triple: [Mr. Prospector, leadingSireTitle, North America leading sire 1987]
-
A.
sonTitle
Indicates that the object is a title or form of address specifically associated with the subject in their role as a son.
-
B.
leaderMayHoldTitle
Indicates that a leader is permitted or able to possess or be designated by a particular formal title.
-
C.
isSeniorTitle
Indicates that one title holds a higher or more senior rank or status relative to another title.
-
D.
recognizedHeirTitle
Indicates that an individual is formally acknowledged as the legitimate holder or successor of a specific hereditary title.
-
E.
laterTitleOfPatron
Indicates that one title held by a patron chronologically succeeds another title previously held by the same patron.
- 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4be3cbe8c8190ba216eeebfc3cbec |
completed | April 19, 2026, 11:36 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8eefa88190a700c7c1b4213e46 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:25 a.m.