Triple
T12296361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Daimonji |
E293095
|
entity |
| Predicate | fireLightingTime |
P56348
|
FINISHED |
| Object | evening of August 16 |
—
|
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: evening of August 16 | Statement: [Mount Daimonji, fireLightingTime, evening of August 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fireLightingTime Context triple: [Mount Daimonji, fireLightingTime, evening of August 16]
-
A.
fireEffect
Indicates that one entity produces, causes, or is associated with a fire-related impact or consequence on another entity.
-
B.
fireUse
Indicates the use or application of fire by one entity on, with, or for another entity or object.
-
C.
fireBeganAt
chosen
Indicates that the event of a fire starting occurred at a specific time or location.
-
D.
fireType
Indicates that one entity has a specific classification or category related to fire (e.g., type, kind, or nature of fire).
-
E.
fireProperty
Indicates that one entity possesses or is characterized by a specific property related to fire (such as flammability, combustion behavior, or fire-related attributes).
- 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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec02c008190a56aae60a3d9eff6 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:52 p.m.