Triple
T5497712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JB Marine Soccer Club |
E144250
|
entity |
| Predicate | primaryGenderCategories |
P2577
|
FINISHED |
| Object | girls 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: girls teams | Statement: [JB Marine Soccer Club, primaryGenderCategories, girls teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryGenderCategories Context triple: [JB Marine Soccer Club, primaryGenderCategories, girls teams]
-
A.
genderCategories
chosen
Indicates the classification of an entity into one or more gender-related categories or identities.
-
B.
featuredGender
Indicates that a particular gender is highlighted, emphasized, or given primary focus in a given context or presentation.
-
C.
sexOrGender
Indicates that one entity has a specified biological sex or socially constructed gender identity.
-
D.
genderDivision
Indicates a relationship where roles, responsibilities, or categories are separated or distinguished based on gender.
-
E.
genderConfiguration
Indicates how the genders of the involved entities are arranged or combined within a particular relationship or context.
- 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_69c008f5a2748190bce7a39aabf87a6d |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f08c2a4819093e772a1497c7ecc |
completed | March 22, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69c01b052f3c81909f71c6add0f35a6f |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:32 p.m.