Triple
T27579805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carnival of Light |
E699552
|
entity |
| Predicate | reasonForNonRelease |
P178282
|
FINISHED |
| Object | reported opposition from other Beatles or estates |
—
|
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: reported opposition from other Beatles or estates | Statement: [Carnival of Light, reasonForNonRelease, reported opposition from other Beatles or estates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForNonRelease Context triple: [Carnival of Light, reasonForNonRelease, reported opposition from other Beatles or estates]
-
A.
reasonForRelease
Indicates the cause, justification, or circumstance that led to an entity being released.
-
B.
reasonForNonInstallation
Indicates the explanation or cause for why an expected installation did not occur.
-
C.
reasonForNonCommencement
Indicates the explanation or cause for why an expected activity, process, or obligation did not begin.
-
D.
notHeldReason
Indicates the reason or cause why a particular event, action, or state did not occur or was not carried out.
-
E.
reasonForNotCompletion
Indicates the explanation or cause for why a task, process, or obligation was not completed.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: April 27, 2026, 2:02 p.m.