Triple
T20314655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICE TD |
E510346
|
entity |
| Predicate | withdrawalFromRegularService |
P9372
|
FINISHED |
| Object | around 2017 |
—
|
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: around 2017 | Statement: [ICE TD, withdrawalFromRegularService, around 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withdrawalFromRegularService Context triple: [ICE TD, withdrawalFromRegularService, around 2017]
-
A.
supervisedWithdrawalOf
Indicates that one entity oversees and manages the process by which another entity withdraws something (such as funds, resources, or participation) in a controlled or monitored manner.
-
B.
withdrawalRule
Indicates the conditions or constraints that govern when and how a withdrawal action may occur between entities.
-
C.
withdrawalType
Indicates the specific method or category by which a withdrawal is carried out in a given context.
-
D.
withdrawalRequestedBy
Indicates that a withdrawal action has been initiated or requested by a specific entity.
-
E.
withdrewFrom
chosen
Indicates that one entity removed itself or its participation from another entity, context, or arrangement it was previously part of.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67786f4dc8190b02a6c2a4338362d |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:19 a.m.