Triple
T12524271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flame of Peace |
E299394
|
entity |
| Predicate | lightingStatus |
P42109
|
FINISHED |
| Object | continuously burning |
—
|
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: continuously burning | Statement: [Flame of Peace, lightingStatus, continuously burning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lightingStatus Context triple: [Flame of Peace, lightingStatus, continuously burning]
-
A.
lightingControlledBy
Indicates that the lighting system or device is operated, regulated, or influenced by a specified controller or control mechanism.
-
B.
hasLighting
Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
-
C.
lightingRequirement
Indicates the level or type of light that is needed for something to function, grow, or be used properly.
-
D.
illuminationCondition
chosen
Indicates the lighting or brightness conditions under which an event, observation, or interaction takes place.
-
E.
lightType
Indicates the specific category or kind of light associated with an entity or lighting setup.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d9540d7b788190a0d57b098e90e491 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.