Triple
T4836017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amar Jawan Jyoti |
E108060
|
entity |
| Predicate | hasFlameType |
P31578
|
FINISHED |
| Object | eternal flame fueled by LPG |
—
|
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: eternal flame fueled by LPG | Statement: [Amar Jawan Jyoti, hasFlameType, eternal flame fueled by LPG]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlameType Context triple: [Amar Jawan Jyoti, hasFlameType, eternal flame fueled by LPG]
-
A.
hasEternalFlame
Indicates that an entity possesses or maintains a flame that is intended to burn perpetually without being extinguished.
-
B.
isFireFollower
Indicates that an entity follows, worships, or is devoted to fire or a fire-related power or doctrine.
-
C.
isCombustible
Indicates that a substance or material is capable of catching fire and burning under certain conditions.
-
D.
combustionType
chosen
Indicates the specific manner or category of combustion process by which something burns or reacts chemically with an oxidizer.
-
E.
hasPlume
Indicates that an entity possesses or exhibits a plume, such as a feathered tuft, spray, or column-like emission.
- 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c21c7f08190846049d31fdfa144 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.