Triple
T26120767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Frankfurter |
E658957
|
entity |
| Predicate | expelledTo |
P159972
|
FINISHED |
| Object | Liechtenstein |
—
|
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: Liechtenstein | Statement: [David Frankfurter, expelledTo, Liechtenstein]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expelledTo Context triple: [David Frankfurter, expelledTo, Liechtenstein]
-
A.
expelledFrom
Indicates that an entity has been formally forced to leave or is removed from a place, organization, or institution, typically as a punishment or disciplinary action.
-
B.
expulsionEvent
Indicates an event in which an entity is formally forced to leave or is removed from a place, group, or institution.
-
C.
expulsionReason
Indicates the cause or justification for which an entity was expelled from a group, place, or institution.
-
D.
expulsionStart
Indicates the point in time when an expulsion process or event begins.
-
E.
expel
Indicates forcing an entity to leave or be removed from a place, group, or situation, typically as a punishment or consequence.
- 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_69ee5bc2b2948190b458ad3f580af779 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60acb357081909b4d9e869e4d2456 |
completed | May 2, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 8:08 p.m.