Triple
T36256023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Alternative Escape |
E891938
|
entity |
| Predicate | companionEventTo |
P114562
|
FINISHED |
| Object | The Great Escape |
—
|
NE NERFINISHED |
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: The Great Escape | Statement: [The Alternative Escape, companionEventTo, The Great Escape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companionEventTo Context triple: [The Alternative Escape, companionEventTo, The Great Escape]
-
A.
hasCompanionEvent
chosen
Indicates that one event is associated with another event that occurs alongside it as a related or accompanying occurrence.
-
B.
combineEvent
Indicates that two or more events are merged into a single, unified event or outcome.
-
C.
companionOf
Indicates that one entity serves as a companion or partner to another, typically accompanying or being closely associated with them.
-
D.
associatedWithEventHost
Indicates that an entity has a relationship or connection with the host of a particular event.
-
E.
accompaniesTo
Indicates that one entity goes along with or escorts another entity to a specific destination or event.
- 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: May 3, 2026, 4:09 p.m.