Triple
T28262212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | deserts the army for Carmen |
E712610
|
entity |
| Predicate | hasTemporalOrderInWork |
P179919
|
FINISHED |
| Object | beforeBullringScene |
—
|
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: beforeBullringScene | Statement: [deserts the army for Carmen, hasTemporalOrderInWork, beforeBullringScene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTemporalOrderInWork Context triple: [deserts the army for Carmen, hasTemporalOrderInWork, beforeBullringScene]
-
A.
isContainedInWorkBy
Indicates that something is included within, or forms a part of, a larger work created by a specified agent.
-
B.
hasPrecedingWork
Indicates that one work comes before another in a sequence, serving as its predecessor.
-
C.
performedInWorkBy
Indicates that an action or role was carried out within a specific work (e.g., a film, book, or composition) by a particular agent or contributor.
-
D.
hasWorkBasedOn
Indicates that one work is derived from, adapted from, or otherwise based on the content of another work.
-
E.
hasWorkInSeriesRole
Indicates that an entity holds a specific role or function within a particular work that is part of a series.
- 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_69efb5207eb08190827e4c34048030b1 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
| PDg | Predicate description generation | batch_69f72920c6208190aa4aba6cb6193109 |
completed | May 3, 2026, 10:53 a.m. |
Created at: April 27, 2026, 11:12 p.m.