Triple
T1676953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L86 LSW |
E36251
|
entity |
| Predicate | intendedAdvantage |
P635
|
FINISHED |
| Object | greater accuracy at range |
—
|
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: greater accuracy at range | Statement: [L86 LSW, intendedAdvantage, greater accuracy at range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedAdvantage Context triple: [L86 LSW, intendedAdvantage, greater accuracy at range]
-
A.
notableAdvantage
Indicates that one entity possesses a significant benefit, edge, or favorable quality over another entity or in a given context.
-
B.
hasAdvantage
chosen
Indicates that one entity possesses a benefit, edge, or favorable position over another in a given context.
-
C.
primaryBenefit
Indicates that one entity serves as the main or most important advantage, gain, or positive outcome associated with another entity.
-
D.
exclusiveBenefit
Indicates that a benefit is provided to one party or group in a way that excludes others from receiving the same advantage.
-
E.
intendedPower
Indicates the level or amount of power that an entity is designed, planned, or expected to produce, use, or deliver under intended operating conditions.
- 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.