Triple
T38387367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mythical kingdom of Allemonde |
E899613
|
entity |
| Predicate | firstPerformanceVenueOfWorkSetting |
P43663
|
FINISHED |
| Object | Opéra-Comique, Paris |
E189257
|
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: Opéra-Comique, Paris | Statement: [mythical kingdom of Allemonde, firstPerformanceVenueOfWorkSetting, Opéra-Comique, Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPerformanceVenueOfWorkSetting Context triple: [mythical kingdom of Allemonde, firstPerformanceVenueOfWorkSetting, Opéra-Comique, Paris]
-
A.
firstPerformanceLocationOfWorkAppearingIn
Indicates the location where a work was first performed or premiered.
-
B.
firstPerformancePlaceOfWork
Indicates the place of work where an entity had its first performance or debut.
-
C.
firstPerformanceCityOfWork
Indicates the city where a particular work was first performed.
-
D.
firstPerformanceTheatre
Indicates the theatre where an entity (such as a play or performance) was first performed.
-
E.
originalPerformanceVenue
chosen
Indicates the venue where a performance was first originally presented or premiered.
- 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_69f76e5c9b808190b486523f5c2f817d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41c27d67d48190a5ec104c2473a372 |
completed | June 29, 2026, 12:55 a.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.