Triple
T36350631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triple Crown 2004 |
E895191
|
entity |
| Predicate | isTraditionalHonor |
P185412
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Triple Crown 2004, isTraditionalHonor, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTraditionalHonor Context triple: [Triple Crown 2004, isTraditionalHonor, true]
-
A.
isTraditional
Indicates that something adheres to long-established customs, practices, or norms rather than modern or innovative ones.
-
B.
isHonor
Indicates that one entity is regarded as an honor, distinction, or source of prestige for another entity.
-
C.
isTraditionOf
Indicates that something is a customary practice, belief, or ritual associated with or belonging to a particular group, culture, or context.
-
D.
isHonorific
Indicates that one entity functions as an honorific title or respectful form of address applied to another entity.
-
E.
hasHonorificSystem
Indicates that a language or culture employs a structured system of honorifics to mark social status, respect, or formality in communication.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be9b9ab481908328e0e8d8ac73d4 |
completed | May 3, 2026, 9:31 p.m. |
Created at: May 3, 2026, 4:09 p.m.