Triple
T37092005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PEP 649 |
E918446
|
entity |
| Predicate | withdrawnInFavorOf |
P29119
|
FINISHED |
| Object | PEP 695 |
—
|
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: PEP 695 | Statement: [PEP 649, withdrawnInFavorOf, PEP 695]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withdrawnInFavorOf Context triple: [PEP 649, withdrawnInFavorOf, PEP 695]
-
A.
withdrewInFavorOf
chosen
Indicates that one party retracted or gave up its position, claim, or candidacy in support of another party.
-
B.
withdrawn
Indicates that an entity has removed or taken back a previously offered, submitted, or available item, action, or commitment.
-
C.
dissolvedInFavorOf
Indicates that one entity has been formally terminated, annulled, or discontinued in order to benefit, support, or be replaced by another entity.
-
D.
withdrawnDuring
Indicates that something is removed, canceled, or taken back over the course of a specified time period or event.
-
E.
withdrawnAsStandard
Indicates that a previously recognized standard has been officially withdrawn and is no longer in active use or recommended status.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.