Triple
T18873125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Works Council |
E461618
|
entity |
| Predicate | recastIn |
P133288
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [European Works Council, recastIn, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recastIn Context triple: [European Works Council, recastIn, 2009]
-
A.
recastBy
Indicates that an existing role, character, or part has been newly assigned to a different performer or entity than before.
-
B.
recastOf
Indicates that one entity is a new or different version, adaptation, or reinterpretation of another, typically replacing or redoing the original in a similar role or context.
-
C.
recutIn
Indicates that an item has been cut again or re-edited into a new version, typically after an initial cutting or editing process.
-
D.
reconstructedIn
Indicates that something has been rebuilt, restored, or re-created within a particular context, location, or medium.
-
E.
recastInYear
Indicates that an existing work, role, or production was cast again with different performers in a specified year.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c2ab4bb4819086ae98a38dd9b11b |
completed | April 20, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69e48d22dde8819093b1d963bd673365 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:57 a.m.