Triple
T27739913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tag Team Division |
E701823
|
entity |
| Predicate | includesGenderDivision |
P49314
|
FINISHED |
| Object | men's tag 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 tag teams | Statement: [Tag Team Division, includesGenderDivision, men's tag teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesGenderDivision Context triple: [Tag Team Division, includesGenderDivision, men's tag teams]
-
A.
hasGenderDivisions
chosen
Indicates that something is organized, classified, or separated into groups based on gender.
-
B.
genderDivision
Indicates a relationship where roles, responsibilities, or categories are separated or distinguished based on gender.
-
C.
alsoIncludesGenderOfDivers
Indicates that the referenced set or category additionally encompasses the gender identity of divers.
-
D.
genderCategoryIncludes
Indicates that a given gender category encompasses or contains the specified gender identity or subgroup.
-
E.
hasGenderDistinction
Indicates that a relationship, classification, or linguistic form differentiates entities based on gender categories.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: April 27, 2026, 4:09 p.m.