Triple
T34091883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acomplia |
E874318
|
entity |
| Predicate | withdrawnInRegion |
P46697
|
FINISHED |
| Object | European Union |
—
|
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: European Union | Statement: [Acomplia, withdrawnInRegion, European Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withdrawnInRegion Context triple: [Acomplia, withdrawnInRegion, European Union]
-
A.
withdrawn
chosen
Indicates that an entity has removed or taken back a previously offered, submitted, or available item, action, or commitment.
-
B.
withdrawnDuring
Indicates that something is removed, canceled, or taken back over the course of a specified time period or event.
-
C.
withdrawingCountry
Indicates that a country is in the process of or has decided to withdraw from a group, agreement, organization, or arrangement.
-
D.
withdrawnAsStandard
Indicates that a previously recognized standard has been officially withdrawn and is no longer in active use or recommended status.
-
E.
withdrewFrom
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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70c16095081908ffa34ea55556a65 |
completed | May 3, 2026, 8:49 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:52 a.m.