Triple
T1250017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carcano rifle |
E26852
|
entity |
| Predicate | inServiceUntil |
P6544
|
FINISHED |
| Object | 1945 |
—
|
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: 1945 | Statement: [Carcano rifle, inServiceUntil, 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inServiceUntil Context triple: [Carcano rifle, inServiceUntil, 1945]
-
A.
inService
Indicates that an entity is currently active, operational, or available for use in its intended role or function.
-
B.
commissionedInService
Indicates that an entity was formally brought into active service or duty within a particular organization, role, or context.
-
C.
usedUntil
chosen
Indicates that something remained in use or operation up to a specified time or event, after which it was no longer used.
-
D.
inForceUntil
Indicates that a condition, rule, or agreement remains valid and operative up to a specified time or event.
-
E.
serviceDuring
Indicates that one entity performs or provides a service for another entity during a specified time period or event.
- 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf84c73c8190bbb14265cd7ab6ae |
completed | March 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6b075881908e867c25b5080e25 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.