Triple
T10341278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TFEU Article 101 |
E243131
|
entity |
| Predicate | previousNumbering |
P39998
|
FINISHED |
| Object | Article 81 EC Treaty |
—
|
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 81 EC Treaty | Statement: [TFEU Article 101, previousNumbering, Article 81 EC Treaty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousNumbering Context triple: [TFEU Article 101, previousNumbering, Article 81 EC Treaty]
-
A.
numberingType
Indicates the scheme or style used to assign sequential numbers or labels within an ordered set.
-
B.
laterNumber
Indicates that one number occurs or is positioned later than another in a specified ordering or sequence.
-
C.
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).
-
D.
precedesNumeral
chosen
Indicates that one numeral comes before another numeral in a specified ordering or sequence.
-
E.
frontNumbering
Indicates that an entity is assigned a numbering or label that appears at the front or beginning of something (e.g., a sequence, document, or list).
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e91fdb2081909866c6ecf417d75a |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4df9dc3208190bf1bd106f44f6202 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:55 a.m.