Triple
T27930142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terry Anderson |
E707956
|
entity |
| Predicate | endTimeOfEvent |
P145529
|
FINISHED |
| Object | 1991 release from captivity in Lebanon |
—
|
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: 1991 release from captivity in Lebanon | Statement: [Terry Anderson, endTimeOfEvent, 1991 release from captivity in Lebanon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endTimeOfEvent Context triple: [Terry Anderson, endTimeOfEvent, 1991 release from captivity in Lebanon]
-
A.
eventEndTime
chosen
Indicates the specific time at which an event concludes or is considered finished.
-
B.
organizedEventEndTime
Indicates the time at which an organized event is scheduled or recorded to end.
-
C.
eventEndDateAtSite
Indicates that an event concludes on a specific date at a particular site or location.
-
D.
endEvent
Indicates that one event or process marks the termination or conclusion of another event or process.
-
E.
typicallyEndsAt
Indicates that an event, process, or activity most commonly or usually concludes at a particular time, place, or state.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 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. |
Created at: April 27, 2026, 7:02 p.m.