Triple
T16119471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mauser 1893 rifle |
E391094
|
entity |
| Predicate | magazineConfiguration |
P121554
|
FINISHED |
| Object | staggered-column |
—
|
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: staggered-column | Statement: [Mauser 1893 rifle, magazineConfiguration, staggered-column]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: magazineConfiguration Context triple: [Mauser 1893 rifle, magazineConfiguration, staggered-column]
-
A.
magazineType
Indicates the specific category or genre to which a magazine belongs.
-
B.
relationshipToMagazine
Indicates the type of connection or association an entity has with a particular magazine, such as authorship, editorship, or other defined roles or links.
-
C.
compatibleMagazines
Indicates that two magazines can be used together or interchangeably without conflict or issues.
-
D.
isMagazineFed
Indicates that an object receives its ammunition or items through a detachable or fixed magazine mechanism.
-
E.
transitionedToWeeklyMagazine
Indicates that an entity changed its publication frequency or format to become a weekly magazine.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2016d527c8190928e73661b18a914 |
completed | April 17, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e183b9d3f08190953ada68f4272996 |
completed | April 17, 2026, 12:50 a.m. |
Created at: April 10, 2026, 5 a.m.