Triple
T2227373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Maroons |
E48682
|
entity |
| Predicate | genderInclusiveProgram |
P36340
|
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: [Chicago Maroons, genderInclusiveProgram, men's teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderInclusiveProgram Context triple: [Chicago Maroons, genderInclusiveProgram, men's teams]
-
A.
genderEquality
Indicates that the relationship or action promotes, reflects, or ensures equal rights, opportunities, and treatment for all genders without discrimination.
-
B.
admissionGender
Indicates the gender-based criteria or classification applied in the context of admission or entry decisions.
-
C.
usesGenderAccurateLanguage
Indicates that the language employed in the context correctly reflects and respects the gender identities of the entities referenced.
-
D.
sponsoredPrograms
Indicates that an entity provides financial or resource support to specific programs or initiatives.
-
E.
establishedProgram
Indicates that an entity has created and put into operation a formal program that is now in an active, ongoing state.
- 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0670ce48190b98814064bff0517 |
completed | March 7, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69abbdadbb0c8190b3a1ede31b8acbfa |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe4252688190944491a450383450 |
completed | March 7, 2026, 5:57 a.m. |
Created at: March 4, 2026, 7:47 p.m.