Triple
T10384505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dangan Castle |
E244724
|
entity |
| Predicate | fireOccurredIn |
P76120
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Dangan Castle, fireOccurredIn, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fireOccurredIn Context triple: [Dangan Castle, fireOccurredIn, 19th century]
-
A.
fireIncidentRelated
Indicates that there is a connection or association between a specific fire incident and another entity, event, or record.
-
B.
fireBeganAt
Indicates that the event of a fire starting occurred at a specific time or location.
-
C.
fireType
Indicates that one entity has a specific classification or category related to fire (e.g., type, kind, or nature of fire).
-
D.
fires
Indicates that an agent initiates the discharge or ignition of something, such as a weapon, engine, or explosive device, causing it to operate or go off.
-
E.
fireProblemSince
chosen
Indicates that a fire-related problem has been occurring or has been present since a specific point in time.
- 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9a35fb08190ab85b4a8f8dea511 |
completed | April 7, 2026, 11:25 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb0e7a88190bec0b7a52c70dfe2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:04 p.m.