Triple
T4167614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyle gun |
E84481
|
entity |
| Predicate | powerMethod |
P14386
|
FINISHED |
| Object | gunpowder charge |
—
|
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: gunpowder charge | Statement: [Lyle gun, powerMethod, gunpowder charge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerMethod Context triple: [Lyle gun, powerMethod, gunpowder charge]
-
A.
methodOfRiseToPower
Indicates the manner, strategy, or process by which an entity attained power or authority.
-
B.
primePowerFormula
Indicates that a value is computed using a formula specifically involving powers of prime numbers.
-
C.
powerConversionMethod
Indicates the method or process by which one form of power or energy is converted into another.
-
D.
powerBy
chosen
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
E.
EuclideanFunction
Indicates a relationship defined by a Euclidean distance–based function, typically mapping entities or their attributes to values derived from Euclidean metric properties.
- 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_69aed932cab48190b80ffe35f7029ae1 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af02c43a7481909eed7cb8c14deb0c |
completed | March 9, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69af018fb0948190a9701b2e8e5d9bac |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:44 p.m.