Triple
T35445352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Return from Cythera |
E1024466
|
entity |
| Predicate | appliedToVersionOf |
P1129
|
FINISHED |
| Object | Watteau’s Cythera compositions |
—
|
NE NERFINISHED |
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: Watteau’s Cythera compositions | Statement: [Return from Cythera, appliedToVersionOf, Watteau’s Cythera compositions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToVersionOf Context triple: [Return from Cythera, appliedToVersionOf, Watteau’s Cythera compositions]
-
A.
basedOnVersion
Indicates that one entity is derived from, built upon, or created using a specific version of another entity as its basis.
-
B.
appliesTo
chosen
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
C.
hasVersionFor
Indicates that one entity serves as a specific version or variant tailored for another entity.
-
D.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
E.
introducedVersionOf
Indicates that one entity is the version in which another entity was first introduced or made available.
- 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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff45793d5c81909dc503ad1f714ee2 |
completed | May 9, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69ff41cb0e088190a6e9b03cb20e5fad |
completed | May 9, 2026, 2:16 p.m. |
Created at: May 3, 2026, 4:04 p.m.