Triple
T28309806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enfield No. 2 Mk I |
E713963
|
entity |
| Predicate | standardCalibre |
P81016
|
FINISHED |
| Object | .38/200 British service |
—
|
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: .38/200 British service | Statement: [Enfield No. 2 Mk I, standardCalibre, .38/200 British service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardCalibre Context triple: [Enfield No. 2 Mk I, standardCalibre, .38/200 British service]
-
A.
calibre
Indicates the quality, capability, or degree of excellence associated with an entity in relation to others.
-
B.
primaryCalibre
chosen
Indicates the main or most significant size or capacity of a weapon’s ammunition or armament associated with an entity.
-
C.
standardEditionVolume
Indicates that one entity is a volume that forms part of a standard edition of another entity (such as a work or collection).
-
D.
standardCirculation
Indicates that an item is being borrowed or used under the library’s normal, non-restricted lending rules.
-
E.
standardReference
Indicates that one entity serves as the authoritative or canonical reference or benchmark for interpreting, validating, or comparing another entity.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 27, 2026, 11:39 p.m.