Triple
T19382985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moldova at the Olympic Games |
E484858
|
entity |
| Predicate | includesBothGenders |
P136236
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Moldova at the Olympic Games, includesBothGenders, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesBothGenders Context triple: [Moldova at the Olympic Games, includesBothGenders, true]
-
A.
isUnisex
Indicates that something is suitable, designed, or intended for use by individuals of any gender.
-
B.
isUnisexInSomeRegions
Indicates that the item or concept is considered suitable or applicable to all genders, but only in certain geographic or cultural regions.
-
C.
isUnisexVariantOf
Indicates that one item is a gender-neutral or unisex version or form of another item.
-
D.
hasGenderNeutrality
Indicates that something (such as a term, form, or expression) is neutral with respect to gender and does not specify or imply any particular gender.
-
E.
hasGenderVariant
Indicates that one entity is a gender-specific form or variant of another entity.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61a614cf88190b561eafaa350ce19 |
completed | April 20, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69e50213571881909cd7543a43b51986 |
completed | April 19, 2026, 4:25 p.m. |
Created at: April 10, 2026, 1:35 p.m.