Triple
T16266443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moto3 |
E394886
|
entity |
| Predicate | hasFemaleCompetitors |
P122433
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Moto3, hasFemaleCompetitors, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFemaleCompetitors Context triple: [Moto3, hasFemaleCompetitors, yes]
-
A.
hasFemaleEquivalent
Indicates that one entity serves as the female counterpart or equivalent of another entity.
-
B.
numberOfFemaleAthletes
Indicates the count of athletes who are female in a given context or group.
-
C.
sportGender
Indicates that a sport or sporting event is associated with a particular gender category (e.g., men's, women's, mixed).
-
D.
hasGenderedTeams
Indicates that the entity organizes or participates in teams that are separated or defined based on gender.
-
E.
eligiblePlayersGender
Indicates that the relationship specifies which player genders are allowed or considered eligible in a given context.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c839788190b974d1d0d2525b88 |
completed | April 17, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:05 a.m.