Triple
T7463537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messenger Stakes |
E176312
|
entity |
| Predicate | alsoEligible |
P77264
|
FINISHED |
| Object | fillies with declaration |
—
|
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: fillies with declaration | Statement: [Messenger Stakes, alsoEligible, fillies with declaration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoEligible Context triple: [Messenger Stakes, alsoEligible, fillies with declaration]
-
A.
eligibility
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
-
B.
eligibleOn
Indicates the date or condition from which something qualifies to begin or be considered valid or applicable.
-
C.
eligibleFrom
Indicates that a subject becomes or is considered eligible starting from a specified point in time or condition.
-
D.
positionEligible
Indicates that an entity is qualified or permitted to hold or be assigned to a particular position or role.
-
E.
nonEligibility
Indicates that an entity does not meet the required conditions or criteria to qualify for a specified status, benefit, or action.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d9d25c819087efc772b5b127fa |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f386daac81908ded91b397b44148 |
completed | March 27, 2026, 9:15 p.m. |
Created at: March 27, 2026, 3:39 p.m.