Triple
T24240878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Cambert |
E603218
|
entity |
| Predicate | workPremiere |
P94894
|
FINISHED |
| Object | Pomone premiered in 1671 in Paris |
—
|
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: Pomone premiered in 1671 in Paris | Statement: [Robert Cambert, workPremiere, Pomone premiered in 1671 in Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workPremiere Context triple: [Robert Cambert, workPremiere, Pomone premiered in 1671 in Paris]
-
A.
workPremiereEvent
chosen
Indicates the event at which a creative work is first publicly presented or premiered.
-
B.
premiereWithWork
Indicates that a performance, event, or production debuts at the same time as (or as part of) the first public presentation of a specific work.
-
C.
workPremiereCountry
Indicates the country in which a work (such as a film, play, or musical piece) was first premiered or publicly presented.
-
D.
premiereWork
Indicates that a creative work is the first or debut piece presented or introduced by a particular creator or entity.
-
E.
workFor
Indicates that one entity is employed by or performs work under the authority or direction 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_69e2953f631c819097cbb421046bd417 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28a9f812c81909dba8fbb54d8985c |
completed | April 29, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:03 a.m.