Triple
T37213466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shrek 3-D |
E922669
|
entity |
| Predicate | continuesEventsOf |
P193961
|
FINISHED |
| Object | Shrek (2001 film) |
—
|
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: Shrek (2001 film) | Statement: [Shrek 3-D, continuesEventsOf, Shrek (2001 film)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuesEventsOf Context triple: [Shrek 3-D, continuesEventsOf, Shrek (2001 film)]
-
A.
continuityEvent
chosen
Indicates that one event maintains narrative or temporal continuity with another, linking them as part of the same ongoing sequence or storyline.
-
B.
continuesActivitiesAs
Indicates that an entity carries on or maintains the same activities, roles, or functions previously performed by another entity.
-
C.
coversEventsAfter
Indicates that one event or time interval extends to include all events occurring after a specified reference event or time.
-
D.
continuesFor
Indicates that an event, state, or process persists or remains in effect for a specified duration or period.
-
E.
continuesOn
Indicates that an action, process, or state persists or carries forward beyond a given point, without interruption or termination.
- 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_69f76ea6f5288190b8d9988f613811c0 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: May 3, 2026, 4:15 p.m.