Triple
T32442969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AIFF Player of the Year |
E829062
|
entity |
| Predicate | hasGenderSpecificVersion |
P48671
|
FINISHED |
| Object | AIFF Women’s Player of the Year |
—
|
NE NERFINISHED |
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: AIFF Women’s Player of the Year | Statement: [AIFF Player of the Year, hasGenderSpecificVersion, AIFF Women’s Player of the Year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenderSpecificVersion Context triple: [AIFF Player of the Year, hasGenderSpecificVersion, AIFF Women’s Player of the Year]
-
A.
hasGenderVariant
chosen
Indicates that one entity is a gender-specific form or variant of another entity.
-
B.
hasGenderDistinction
Indicates that a relationship, classification, or linguistic form differentiates entities based on gender categories.
-
C.
hasGenderFormat
Indicates that something is associated with or expressed in a particular gender-related format or representation.
-
D.
hasGenderConvention
Indicates that there is an established or customary way of assigning or expressing gender within a given context, system, or culture.
-
E.
hasGenderInterpretation
Indicates that an entity is associated with a particular interpretation or understanding of gender.
- 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 1, 2026, 12:55 a.m.