Triple
T33513669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qualification Directive |
E858309
|
entity |
| Predicate | recastEnteredIntoForce |
P177057
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Qualification Directive, recastEnteredIntoForce, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recastEnteredIntoForce Context triple: [Qualification Directive, recastEnteredIntoForce, 2011]
-
A.
charterEnteredIntoForce
Indicates that a charter has become legally effective and binding as of a specific point in time.
-
B.
recastIn
Indicates that an entity has been assigned or transformed into a new role, form, or representation, replacing or altering its previous casting or configuration.
-
C.
recast
Indicates that an entity is assigned a new role or form, replacing a previous assignment or interpretation in a given context.
-
D.
recastBy
Indicates that an existing role, character, or part has been newly assigned to a different performer or entity than before.
-
E.
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.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f814fcf48190ae4504154d1b2c05 |
completed | May 3, 2026, 7:24 a.m. |
Created at: May 1, 2026, 1:39 a.m.