Triple
T36075709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ERS |
E1043489
|
entity |
| Predicate | hasEnergyDeploymentLimitPerLap |
P195066
|
FINISHED |
| Object | 4 MJ (approximate, FIA-regulated) |
—
|
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: 4 MJ (approximate, FIA-regulated) | Statement: [ERS, hasEnergyDeploymentLimitPerLap, 4 MJ (approximate, FIA-regulated)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnergyDeploymentLimitPerLap Context triple: [ERS, hasEnergyDeploymentLimitPerLap, 4 MJ (approximate, FIA-regulated)]
-
A.
capacityPerCycle
Indicates the amount of output or throughput that can be achieved during a single operational cycle of a process or system.
-
B.
hasVariableSpeedLimits
Indicates that the subject is associated with speed limits that can change depending on conditions, time, or location.
-
C.
rideLimit
Indicates a constraint on the maximum number, duration, or frequency of rides permitted for an entity.
-
D.
hasPowerCapacity
Indicates that an entity possesses a specified amount or limit of power it can produce, handle, or store.
-
E.
isRunEnergyOf
Indicates that a specified value represents the run energy associated with a particular entity or agent.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
| PDg | Predicate description generation | batch_69fd9fef7aac819089cc88dd3d00296d |
completed | May 8, 2026, 8:33 a.m. |
Created at: May 3, 2026, 4:08 p.m.