Triple
T33475471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Tech Bears |
E857308
|
entity |
| Predicate | sportGenderCategories |
P7453
|
FINISHED |
| Object | men's teams |
—
|
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: men's teams | Statement: [New York Tech Bears, sportGenderCategories, men's teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportGenderCategories Context triple: [New York Tech Bears, sportGenderCategories, men's teams]
-
A.
sportGender
chosen
Indicates that a sport or sporting event is associated with a particular gender category (e.g., men's, women's, mixed).
-
B.
sportCategory
Indicates that one entity is classified as a type or category of sport to which the other entity (typically a specific sport or sporting event) belongs.
-
C.
sportsCategory
Indicates that one entity is classified as a type or category within the domain of sports to which the other entity belongs.
-
D.
hasFemaleCompetitors
Indicates that an entity participates in a competitive context where at least some of the competitors are female.
-
E.
genderOfCompetitors
Indicates the gender category or composition of the participants involved in a competition or competitive event.
- 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_69f3497472508190b300ebd3fd402367 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:38 a.m.