Triple
T10983649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gewehr 98 |
E259570
|
entity |
| Predicate | standardIssueFrom |
P96452
|
FINISHED |
| Object | 1898 |
—
|
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: 1898 | Statement: [Gewehr 98, standardIssueFrom, 1898]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardIssueFrom Context triple: [Gewehr 98, standardIssueFrom, 1898]
-
A.
standardIssueFor
Indicates that something is the typical or officially designated item or version provided for use in a particular context, role, or organization.
-
B.
standardCreated
Indicates that an entity is responsible for the creation or establishment of a particular standard.
-
C.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
D.
standardFormBasedIn
Indicates that a standardized form or format is established, defined, or grounded in a particular source, basis, or reference framework.
-
E.
issueType
Indicates the specific category or classification assigned to an issue within a tracking or management context.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d772ec55fc81909b2b15f2493dddc6 |
completed | April 9, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
| PDg | Predicate description generation | batch_69d732242fdc8190be77d1f730a42935 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:24 p.m.