Triple
T35537743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RIIO-ED2 |
E1026974
|
entity |
| Predicate | RIIOAcronymExpansion |
P42398
|
FINISHED |
| Object | Revenue = Incentives + Innovation + Outputs |
—
|
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: Revenue = Incentives + Innovation + Outputs | Statement: [RIIO-ED2, RIIOAcronymExpansion, Revenue = Incentives + Innovation + Outputs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RIIOAcronymExpansion Context triple: [RIIO-ED2, RIIOAcronymExpansion, Revenue = Incentives + Innovation + Outputs]
-
A.
RIR
Indicates a reciprocal or mutual relationship between two entities, where each stands in the same relation to the other.
-
B.
RIC
Indicates a relationship in which one entity is responsible for insuring or providing insurance coverage to another entity or asset.
-
C.
acronymExpansion
chosen
Indicates that one term is an acronym whose letters stand for the words in another, longer expression.
-
D.
hasRIO
Indicates that an entity is associated with, or possesses, a specific Region of Interest (RIO) in a given context.
-
E.
RIFXMeaning
Indicates that one entity represents the meaning, interpretation, or semantic content associated with another entity.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.