Triple
T13133687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Van Gend en Loos |
E312026
|
entity |
| Predicate | articleInterpretedCurrentNumbering |
P17113
|
FINISHED |
| Object | Article 30 TFEU |
—
|
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: Article 30 TFEU | Statement: [Van Gend en Loos, articleInterpretedCurrentNumbering, Article 30 TFEU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: articleInterpretedCurrentNumbering Context triple: [Van Gend en Loos, articleInterpretedCurrentNumbering, Article 30 TFEU]
-
A.
numberingStatus
Indicates the status or condition of an entity’s assigned number or numbering process (e.g., whether it has been numbered, is pending, or has a particular numbering state).
-
B.
numberingType
Indicates the scheme or style used to assign sequential numbers or labels within an ordered set.
-
C.
legalNumbering
Indicates that an entity has an officially assigned legal or regulatory identification number.
-
D.
numberingDirection
Indicates the direction or order in which items are sequentially numbered within a set or structure.
-
E.
articleNumber
chosen
Indicates that one entity is identified or referenced by a specific article number assigned to it.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981b3d72c8190b69ae56435a954fa |
completed | April 10, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69d9804543cc8190a23cd7da59a12a7b |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:08 p.m.