Triple
T16546711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three-Line Rifle |
E401960
|
entity |
| Predicate | wasStandardIssueFor |
P13409
|
FINISHED |
| Object | Russian infantry |
—
|
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: Russian infantry | Statement: [Three-Line Rifle, wasStandardIssueFor, Russian infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasStandardIssueFor Context triple: [Three-Line Rifle, wasStandardIssueFor, Russian infantry]
-
A.
wasIssueAt
Indicates that a particular issue existed or occurred at a specific time, place, or contextual point.
-
B.
becameStandardIssueByYear
Indicates that an item started being officially issued as standard equipment by a specified year.
-
C.
isStandardOf
Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
-
D.
standardIssueFor
chosen
Indicates that something is the typical or officially designated item or version provided for use in a particular context, role, or organization.
-
E.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fbe3fb48190bad143b50dc73c7e |
completed | April 18, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.