Triple
T9288850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disclosure Guidance and Transparency Rules |
E223464
|
entity |
| Predicate | DTR 7Focus |
P69178
|
FINISHED |
| Object | corporate governance statements |
—
|
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: corporate governance statements | Statement: [Disclosure Guidance and Transparency Rules, DTR 7Focus, corporate governance statements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DTR 7Focus Context triple: [Disclosure Guidance and Transparency Rules, DTR 7Focus, corporate governance statements]
-
A.
testedDevice
Indicates that one entity has performed a test on, or experimentally evaluated, another entity as a device.
-
B.
formerFocus
Indicates that an entity previously served as the primary focus or main subject of attention, but no longer holds that status.
-
C.
partCFocus
chosen
Indicates that a specific part or component of an entity is the primary focus or point of attention in a given context.
-
D.
Typer
Indicates that one entity serves as the type or classification for another entity.
-
E.
deviceIndicates
Indicates that a device provides a signal, status, or output that conveys information about a condition, event, or state.
- 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0862b34c819097cb7c1777313925 |
completed | April 1, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:35 p.m.