Triple
T35378420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 12 EEC Treaty |
E1022577
|
entity |
| Predicate | directEffectRecognizedIn |
P123985
|
FINISHED |
| Object | Van Gend en Loos judgment |
—
|
NE NERFINISHED |
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: Van Gend en Loos judgment | Statement: [Article 12 EEC Treaty, directEffectRecognizedIn, Van Gend en Loos judgment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directEffectRecognizedIn Context triple: [Article 12 EEC Treaty, directEffectRecognizedIn, Van Gend en Loos judgment]
-
A.
recognitionEffectOn
Indicates the effect or consequence that an act of recognition by one entity has on another entity or state.
-
B.
capturesEffectOf
Indicates that one entity represents or records the impact, consequence, or outcome produced by another entity or process.
-
C.
canonicalEffect
Indicates the standard or primary effect that an action, event, or entity is typically understood to produce.
-
D.
hasDirectEffect
chosen
Indicates that one entity produces an immediate and unmediated impact or change on another entity.
-
E.
recognizedSee
Indicates that one entity sees another and consciously recognizes or identifies what is being seen.
- 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_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: May 3, 2026, 4:03 p.m.