Triple
T30484467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vivian |
E775677
|
entity |
| Predicate | hasMasculineUsage |
P152652
|
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: [Vivian, hasMasculineUsage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMasculineUsage Context triple: [Vivian, hasMasculineUsage, true]
-
A.
hasMasculineForm
Indicates that an entity has a corresponding masculine grammatical or lexical form.
-
B.
hasAlternativeGenderUsage
chosen
Indicates that an entity is used with a different or non-standard gender form in certain contexts or usages.
-
C.
hasGenderDistinction
Indicates that a relationship, classification, or linguistic form differentiates entities based on gender categories.
-
D.
hasFemaleFormOf
Indicates that one entity is the specifically female version or form of another, more general or differently gendered entity.
-
E.
hasGenderVariant
Indicates that one entity is a gender-specific form or variant of another entity.
- 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ffaa7bc45c8190b907db8579244a7b |
completed | May 9, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69ffa9f6c9a481908fbd4d18b311cbe2 |
completed | May 9, 2026, 9:41 p.m. |
Created at: April 29, 2026, 8:13 p.m.