Triple
T24240839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pomone |
E603217
|
entity |
| Predicate | firstRunDuration |
P18978
|
FINISHED |
| Object | about 146 performances |
—
|
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: about 146 performances | Statement: [Pomone, firstRunDuration, about 146 performances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRunDuration Context triple: [Pomone, firstRunDuration, about 146 performances]
-
A.
firstRunTimePeriod
Indicates the initial time span or interval during which something first occurs, operates, or is in effect.
-
B.
firstRunAt
Indicates the date and time at which an entity was first executed, launched, or run.
-
C.
durationInitial
chosen
Indicates the initial length of time associated with an event, state, or process at its starting point.
-
D.
firstMovementDuration
Indicates the length of time that the first movement or initial segment of an event, work, or process lasts.
-
E.
firstRunMedium
Indicates that an entity’s initial or earliest run, showing or execution occurred in a specified medium or channel.
- 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.