Triple
T10521752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TFEU Article 106 |
E248189
|
entity |
| Predicate | systematicallyLinkedTo |
P37
|
FINISHED |
| Object | TFEU Article 14 |
—
|
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: TFEU Article 14 | Statement: [TFEU Article 106, systematicallyLinkedTo, TFEU Article 14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systematicallyLinkedTo Context triple: [TFEU Article 106, systematicallyLinkedTo, TFEU Article 14]
-
A.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
-
B.
associatedSystem
Indicates that one entity is functionally or contextually linked to a particular system with which it interacts or to which it belongs.
-
C.
linkedByStructure
Indicates that two entities are connected or associated through a shared structural element, configuration, or framework.
-
D.
expansionLinkedTo
Indicates that one entity’s growth, increase, or enlargement is causally or logically connected to the expansion of another entity.
-
E.
associatedWithSee
Indicates a relationship where one entity is contextually or functionally linked to another through the act or concept of seeing or visual observation.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509dec25881909bc748640f26a416 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:29 p.m.