Triple
T28309328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Paris Lee |
E713952
|
entity |
| Predicate | inventionUsedIn |
P164255
|
FINISHED |
| Object | British service rifles |
—
|
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: British service rifles | Statement: [James Paris Lee, inventionUsedIn, British service rifles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inventionUsedIn Context triple: [James Paris Lee, inventionUsedIn, British service rifles]
-
A.
usedInventionOf
Indicates that one entity made use of, applied, or implemented the invention created by another entity.
-
B.
isFamouslyUsedIn
Indicates that something is widely recognized or well-known for being used in a particular context, work, or situation.
-
C.
inventionCommercializedBy
Indicates that an invention has been brought to market or otherwise commercially exploited by a particular entity.
-
D.
eraUsedIn
Indicates that something (such as a method, standard, or practice) was in active use during a specified historical or temporal era.
-
E.
isFamouslyUsedBy
Indicates that something is widely and notably used by a particular person, group, or entity, in a way that is broadly recognized or associated with them.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f644e0e9e48190818f7bf2204ec741 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f6430975b481909191219ad13ef77e |
completed | May 2, 2026, 6:31 p.m. |
Created at: April 27, 2026, 11:39 p.m.