Triple
T19549473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Single European Act |
E489159
|
entity |
| Predicate | setDeadlineFor |
P8546
|
FINISHED |
| Object | completion of the internal market |
—
|
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: completion of the internal market | Statement: [Single European Act, setDeadlineFor, completion of the internal market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setDeadlineFor Context triple: [Single European Act, setDeadlineFor, completion of the internal market]
-
A.
postDeadlineRule
Indicates a rule or policy that applies to actions or conditions occurring after a specified deadline has passed.
-
B.
hasDeadline
chosen
Indicates that an entity is associated with a specific due date or time by which it must be completed or fulfilled.
-
C.
facesDeadline
Indicates that an entity is approaching or subject to a specific due date or time limit by which a task or obligation must be completed.
-
D.
settlementPeriod
Indicates the length of time between a transaction or agreement and its final settlement or completion.
-
E.
extendsUntil
Indicates that something continues or remains in effect up to a specified point or limit in time or space.
- 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63d2f39188190976e8b6b111499a0 |
completed | April 20, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.