Triple
T38387366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mythical kingdom of Allemonde |
E899613
|
entity |
| Predicate | firstPerformanceOfWorkSetting |
P204632
|
FINISHED |
| Object | 30 April 1902 |
—
|
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: 30 April 1902 | Statement: [mythical kingdom of Allemonde, firstPerformanceOfWorkSetting, 30 April 1902]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPerformanceOfWorkSetting Context triple: [mythical kingdom of Allemonde, firstPerformanceOfWorkSetting, 30 April 1902]
-
A.
firstPerformanceWork
Indicates that a performance is the debut or initial presentation of a particular work.
-
B.
firstPerformancePlaceOfWork
Indicates the place of work where an entity had its first performance or debut.
-
C.
firstPerformance
Indicates that an entity marks the initial or debut performance of another entity, such as a work, artist, or production.
-
D.
firstPerformanceTheatre
Indicates the theatre where an entity (such as a play or performance) was first performed.
-
E.
firstPerformanceOfWorkAppearedIn
Indicates that a given performance is the earliest known or documented performance in which a particular work was presented or appeared.
- F. None of above. chosen
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_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:31 p.m.