Triple
T38599356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Women Are Like That |
E934166
|
entity |
| Predicate | referredWorkForm |
P36545
|
FINISHED |
| Object | opera buffa |
—
|
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: opera buffa | Statement: [Women Are Like That, referredWorkForm, opera buffa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referredWorkForm Context triple: [Women Are Like That, referredWorkForm, opera buffa]
-
A.
relatedWorkForm
Indicates a relationship in which one work is connected to another through a different form or version (e.g., adaptation, translation, or other format variation).
-
B.
formsSingleWorkWith
Indicates that two or more entities combine or collaborate to create a single, unified work.
-
C.
formOfWork
chosen
Indicates that one creative work is a specific form, version, or expression of another related work.
-
D.
referenceForm
Indicates that one entity serves as a reference or canonical form for another entity, typically used as the standard or authoritative version to which others relate.
-
E.
referredWorkKeyCharacteristic
Indicates that the referenced work is associated with a specific key characteristic or defining feature.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
Created at: May 3, 2026, 4:32 p.m.