Triple
T28309803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enfield No. 2 Mk I |
E713963
|
entity |
| Predicate | originatingFactory |
P160003
|
FINISHED |
| Object | Enfield Lock |
—
|
NE NERFINISHED |
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: Enfield Lock | Statement: [Enfield No. 2 Mk I, originatingFactory, Enfield Lock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatingFactory Context triple: [Enfield No. 2 Mk I, originatingFactory, Enfield Lock]
-
A.
originatingService
Indicates the service from which an action, request, or piece of data was initially generated or sent.
-
B.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
C.
machineOrigin
chosen
Indicates that one entity is the source, creator, or place of manufacture for a machine-related entity.
-
D.
constructionOrigin
Indicates the source, cause, or initiating factor from which a construction or building project originates.
-
E.
classOrigin
Indicates the original class or category from which an entity is derived, instantiated, or classified.
- 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_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
Created at: April 27, 2026, 11:39 p.m.