Triple
T18111200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fillies and Mares |
E433477
|
entity |
| Predicate | definesEligibilityBy |
P110232
|
FINISHED |
| Object | sex of the horse |
—
|
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: sex of the horse | Statement: [Fillies and Mares, definesEligibilityBy, sex of the horse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesEligibilityBy Context triple: [Fillies and Mares, definesEligibilityBy, sex of the horse]
-
A.
eligibility
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
-
B.
eligibilityRulesSetBy
Indicates that one party defines or establishes the criteria or rules determining another party’s eligibility for something.
-
C.
mayProvideEligibilityFor
chosen
Indicates that one entity can serve as a basis or qualifying factor that makes another entity eligible for something (such as a benefit, status, or action).
-
D.
eligibilityContext
Indicates the situational or conditional factors under which an entity qualifies for or is considered eligible for something.
-
E.
eligibilityLevel
Indicates the degree or tier of qualification an entity has for a given benefit, service, or status.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd2038081909515fb6d17495cbf |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.