Triple
T282460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SALT I |
E5381
|
entity |
| Predicate | laterReducedABMSitesPerSideTo |
P9603
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [SALT I, laterReducedABMSitesPerSideTo, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterReducedABMSitesPerSideTo Context triple: [SALT I, laterReducedABMSitesPerSideTo, 1]
-
A.
reducesTo
Indicates that one expression, structure, or state can be transformed or simplified into another, typically more basic or canonical, form.
-
B.
side2
Indicates that an entity is positioned on, associated with, or corresponds to the second side of another entity or structure.
-
C.
minimizesRoleOf
Indicates that one entity reduces, downplays, or diminishes the importance, influence, or contribution of another entity’s role.
-
D.
retrocededTo
Indicates that control, ownership, or rights over something were returned or transferred back from one entity to another.
-
E.
laterCapacity
Indicates that one entity’s capacity or capability occurs, becomes available, or is realized at a later time than another’s.
- 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25e0c14b48190a5c936bab36180b3 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b77e028819087e606fc321219f7 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25e06dd7c8190a8cbb76cee3c6e4b |
completed | Feb. 28, 2026, 3:16 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.