Triple
T18044690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor |
E431740
|
entity |
| Predicate | fameWithinDomain |
P124443
|
FINISHED |
| Object | American Thoroughbred racing history |
—
|
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: American Thoroughbred racing history | Statement: [Survivor, fameWithinDomain, American Thoroughbred racing history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fameWithinDomain Context triple: [Survivor, fameWithinDomain, American Thoroughbred racing history]
-
A.
fameStatus
Indicates the level or state of public recognition or renown associated with an entity.
-
B.
fameExtent
chosen
Indicates the degree or scope of how widely recognized or renowned an entity is.
-
C.
famePeak
Indicates the time or point at which an entity reaches its highest level of fame or public recognition.
-
D.
fameFor
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
E.
unitOfProminence
Indicates that one entity specifies the unit or scale in which the prominence or significance of another entity is measured or expressed.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4bff13f488190993445769551c9c2 |
completed | April 19, 2026, 11:43 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.