Triple
T871315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Union financial regulators |
E18818
|
entity |
| Predicate | apply |
P4794
|
FINISHED |
| Object | EU financial regulations |
—
|
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: EU financial regulations | Statement: [European Union financial regulators, apply, EU financial regulations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apply Context triple: [European Union financial regulators, apply, EU financial regulations]
-
A.
appliedBy
chosen
Indicates that an action, process, or treatment is carried out or executed by a particular agent or entity.
-
B.
appliesTheory
Indicates that an entity uses or implements a particular theory in analyzing, explaining, or addressing something.
-
C.
misappliedAs
Indicates that something has been used, interpreted, or assigned in an incorrect, inappropriate, or unintended way.
-
D.
appliesAt
Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
-
E.
after
Indicates that one event, state, or action occurs later in time than another, following it in temporal order.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac94d5ac81909feee876696da589 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa89ca008190b50d061ac7fe19f9 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.