Triple
T10796486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RIM-116 RAM |
E254719
|
entity |
| Predicate | Block2Improvements |
P6555
|
FINISHED |
| Object | improved kinematics |
—
|
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: improved kinematics | Statement: [RIM-116 RAM, Block2Improvements, improved kinematics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Block2Improvements Context triple: [RIM-116 RAM, Block2Improvements, improved kinematics]
-
A.
block
Indicates preventing or obstructing another entity’s action, movement, or access.
-
B.
businessImprovementDistrict
Indicates that an area is designated as a business improvement district, where local businesses collectively fund and manage enhancements and services beyond those provided by the municipality.
-
C.
improvesOn
chosen
Indicates that one entity enhances, refines, or performs better than another entity, typically by addressing its limitations or increasing its effectiveness.
-
D.
claimsToImprove
Indicates that one entity asserts or promises that it will enhance, benefit, or make another entity better in some way.
-
E.
hasLightingImprovements
Indicates that an entity has enhancements or upgrades made to its lighting conditions or systems.
- 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d73332dbfc8190904434846957b618 |
completed | April 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69d6f3188f00819094ee8d65b187a333 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.