Triple
T567703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Corps dress uniforms |
E13590
|
entity |
| Predicate | genderUsage |
P15656
|
FINISHED |
| Object | worn by both male and female Marines |
—
|
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: worn by both male and female Marines | Statement: [Marine Corps dress uniforms, genderUsage, worn by both male and female Marines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderUsage Context triple: [Marine Corps dress uniforms, genderUsage, worn by both male and female Marines]
-
A.
genderCategories
Indicates the classification of an entity into one or more gender-related categories or identities.
-
B.
sexOrGender
Indicates that one entity has a specified biological sex or socially constructed gender identity.
-
C.
genderNeutralForm
Indicates that one entity is a gender-neutral linguistic form or expression corresponding to another, more gendered form.
-
D.
hasNeutralPronoun
Indicates that an entity is referred to using a gender-neutral pronoun.
-
E.
hasGenderDistinction
Indicates that a relationship, classification, or linguistic form differentiates entities based on gender categories.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b02da148190b6a9bad3a22d8ec5 |
completed | March 1, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69a494c183b081909304944aa3d0fe8f |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985a2d08819090947895d9439e06 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:33 p.m.