Triple
T31859536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phénice |
E813283
|
entity |
| Predicate | firstPerformanceLocationOfWorkAppearedIn |
P138066
|
FINISHED |
| Object | Paris |
E568
|
NE 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: Paris | Statement: [Phénice, firstPerformanceLocationOfWorkAppearedIn, Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPerformanceLocationOfWorkAppearedIn Context triple: [Phénice, firstPerformanceLocationOfWorkAppearedIn, Paris]
-
A.
firstPerformanceLocationOfWorkAppearingIn
chosen
Indicates the location where a work was first performed or premiered.
-
B.
firstPerformanceOfWorkAppearedIn
Indicates that a given performance is the earliest known or documented performance in which a particular work was presented or appeared.
-
C.
firstPerformanceCityOfWork
Indicates the city where a particular work was first performed.
-
D.
firstPerformancePlaceOfWork
Indicates the place of work where an entity had its first performance or debut.
-
E.
firstPerformanceOfSourceWork
Indicates that the referenced performance is the earliest known or original performance of the specified source work.
- F. None of above.
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_69f348ebf32881908d9439646933dc76 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2e6580209c8190acfded23ba11b2c2 |
completed | June 14, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:53 p.m.