Triple
T8051379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Council notification procedure |
E187680
|
entity |
| Predicate | formalRequirement |
P55752
|
FINISHED |
| Object | notification must be explicit and unequivocal |
—
|
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: notification must be explicit and unequivocal | Statement: [European Council notification procedure, formalRequirement, notification must be explicit and unequivocal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formalRequirement Context triple: [European Council notification procedure, formalRequirement, notification must be explicit and unequivocal]
-
A.
establishedRequirement
Indicates that one entity has formally set or defined a requirement that another entity is expected to satisfy or comply with.
-
B.
proceduralRequirement
Indicates that one entity specifies or imposes a required procedure or process that must be followed by another entity.
-
C.
legalRequirement
Indicates that one entity is obligated by law to perform, provide, or comply with something in relation to another entity or situation.
-
D.
formalization
chosen
Indicates that an informal concept, process, or agreement is being expressed, structured, or codified in a formal, explicit, and often standardized way.
-
E.
evaluationRequirement
Indicates that one entity imposes or specifies conditions under which another entity must be assessed, tested, or evaluated.
- 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_69ca82b15e948190a62fd7af5218426a |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f7aab6481909d4a7cb9eabcd2af |
completed | March 31, 2026, 3:28 a.m. |
| PD | Predicate disambiguation | batch_69cb049a1b9c8190811c396421ebf9c9 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:24 p.m.