Triple
T35378419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 12 EEC Treaty |
E1022577
|
entity |
| Predicate | hasDirectEffectSince |
P123985
|
FINISHED |
| Object | 1963 |
—
|
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: 1963 | Statement: [Article 12 EEC Treaty, hasDirectEffectSince, 1963]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectEffectSince Context triple: [Article 12 EEC Treaty, hasDirectEffectSince, 1963]
-
A.
hasDirectEffect
chosen
Indicates that one entity produces an immediate and unmediated impact or change on another entity.
-
B.
hadEffectUntil
Indicates that an effect or condition held true up to a specific time or event, after which it no longer applied.
-
C.
hasEffectIn
Indicates that one entity produces, causes, or exerts an effect within a specified context, system, or environment.
-
D.
hasEffectNamedAfter
Indicates that an entity has an effect or phenomenon that is named after another entity.
-
E.
hasSubsequentInfluence
Indicates that one entity has an influence or effect that occurs after, and is causally or temporally downstream from, another entity or event.
- 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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff409ff5548190849c2d50e99bd807 |
completed | May 9, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69ff401a5e188190a72f945e910b4a6c |
completed | May 9, 2026, 2:09 p.m. |
Created at: May 3, 2026, 4:03 p.m.