Triple
T16484322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EPR |
E400398
|
entity |
| Predicate | netEfficiency |
P122957
|
FINISHED |
| Object | around 36–37 percent |
—
|
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: around 36–37 percent | Statement: [EPR, netEfficiency, around 36–37 percent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: netEfficiency Context triple: [EPR, netEfficiency, around 36–37 percent]
-
A.
maximumEfficiency
Indicates that an entity operates at its highest possible level of performance or productivity under given conditions.
-
B.
netWork
Indicates a relationship where entities are connected or interact within a shared system, structure, or set of links that enables communication or exchange.
-
C.
network
Indicates that one entity is connected to or interacts with another through a system of relationships, communication, or information exchange.
-
D.
networkBand
Indicates the specific frequency band or range within a network over which communication or data transmission occurs.
-
E.
marginEfficiency
Indicates how effectively the margin between revenue and costs is generated or utilized in a given context.
- F. None of above. chosen
Provenance (4 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e05bf448190947b9da15fd29d0a |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:13 a.m.