Triple
T8239362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L1A1 Self-Loading Rifle |
E192491
|
entity |
| Predicate | distinctionFromFNMetricFAL |
P1612
|
FINISHED |
| Object | uses inch-pattern magazines and parts |
—
|
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: uses inch-pattern magazines and parts | Statement: [L1A1 Self-Loading Rifle, distinctionFromFNMetricFAL, uses inch-pattern magazines and parts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distinctionFromFNMetricFAL Context triple: [L1A1 Self-Loading Rifle, distinctionFromFNMetricFAL, uses inch-pattern magazines and parts]
-
A.
distinction
Indicates that one entity is recognized, treated, or classified as different or separate from another.
-
B.
isDistinctFrom
chosen
Indicates that two entities are not identical and can be clearly distinguished from one another.
-
C.
isDistinguishedBy
Indicates that one entity is characterized or set apart from others by a particular feature, quality, or attribute.
-
D.
uniformDistinction
Indicates that a clear and consistent difference is maintained between two or more entities within a given context.
-
E.
distinguishesGrade
Indicates that an entity differentiates or sets apart one grade or level from 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_69ca82dc8f148190a2c75a98501a7b91 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb783cce5c8190bf116704d2923ade |
completed | March 31, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:47 p.m.