Triple
T35128982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rule 19 – Intervention |
E1014385
|
entity |
| Predicate | typeOfInterestRequired |
P152915
|
FINISHED |
| Object | actual legal interest |
—
|
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: actual legal interest | Statement: [Rule 19 – Intervention, typeOfInterestRequired, actual legal interest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfInterestRequired Context triple: [Rule 19 – Intervention, typeOfInterestRequired, actual legal interest]
-
A.
subjectInterest
Indicates that the subject has an interest in, or is concerned with, the object.
-
B.
hasInterestType
chosen
Indicates that an entity is associated with a specific category or type of interest it holds or is concerned with.
-
C.
primaryInterest
Indicates that one entity is the main or most significant focus of attention, concern, or engagement for another entity.
-
D.
causeOfInterest
Indicates that one entity is the reason or source that brings about another entity’s interest or attention.
-
E.
publicInterestStatus
Indicates that something has been evaluated or designated in terms of its relevance, importance, or impact to the general public or society at large.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a019037edbc8190bdaec436ac2fcec6 |
completed | May 11, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_6a018fe05a34819080068f588b5ff80c |
completed | May 11, 2026, 8:14 a.m. |
Created at: May 3, 2026, 4:02 p.m.