Triple
T35001229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spiros Antonapoulos |
E1009684
|
entity |
| Predicate | isSentTo |
P64262
|
FINISHED |
| Object | mental institution |
—
|
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: mental institution | Statement: [Spiros Antonapoulos, isSentTo, mental institution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSentTo Context triple: [Spiros Antonapoulos, isSentTo, mental institution]
-
A.
sentIn
Indicates that something (such as a message, document, or item) was transmitted or dispatched to a recipient or destination at a particular time or via a particular medium.
-
B.
sentToDestination
chosen
Indicates that something or someone is transferred or dispatched from an origin to a specified destination.
-
C.
sentAs
Indicates that one entity was transmitted, dispatched, or delivered in the form, role, or capacity of another (e.g., an item or message being sent as something specific).
-
D.
sentOver
Indicates that one entity transmitted or dispatched something to another entity, typically across some distance or medium.
-
E.
sentAfter
Indicates that one message or item was sent at a later time than another specified message or item.
- 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_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.