Triple
T1676951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L86 LSW |
E36251
|
entity |
| Predicate | improvedTo |
P4421
|
FINISHED |
| Object | L86A2 |
—
|
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: L86A2 | Statement: [L86 LSW, improvedTo, L86A2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: improvedTo Context triple: [L86 LSW, improvedTo, L86A2]
-
A.
improvesOn
Indicates that one entity enhances, refines, or performs better than another entity, typically by addressing its limitations or increasing its effectiveness.
-
B.
updated
chosen
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
C.
partlyUpgradedTo
Indicates that an entity has undergone an incomplete or partial upgrade to another specified state, version, or configuration.
-
D.
claimsToImprove
Indicates that one entity asserts or promises that it will enhance, benefit, or make another entity better in some way.
-
E.
elevatedTo
Indicates that one entity is promoted or raised to a higher rank, status, position, or level relative to another.
- 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_69a886139ed081909af0940aa9313512 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab272a653481908f48aa1eed5de8a4 |
completed | March 6, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69aa61b2f6288190b2348ef7d7e4672d |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.