Triple
T34167281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamagata Castle |
E876444
|
entity |
| Predicate | garrisonFunctionEnded |
P26563
|
FINISHED |
| Object | late 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: late 19th century | Statement: [Yamagata Castle, garrisonFunctionEnded, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonFunctionEnded Context triple: [Yamagata Castle, garrisonFunctionEnded, late 19th century]
-
A.
garrisonFunction
Indicates that an entity serves as a military garrison or base for another entity, providing housing, support, or operational facilities for its forces.
-
B.
garrisonFunctionReduced
Indicates that the operational capacity or effectiveness of a garrison’s function has been diminished or restricted.
-
C.
garrisonUseUntil
chosen
Indicates that a garrison occupies or utilizes a location or resource up to a specified end time or condition.
-
D.
garrisonAfterWar
Indicates that a military force is stationed in or occupies a location following the end of a war or major conflict.
-
E.
garrisonAfterEvacuation
Indicates that a military force is stationed in a location following a prior evacuation of that location.
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fdfb02481908656f80d4f801ddf |
completed | May 3, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.