Triple
T26615171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Takeda Katsuyori |
E668037
|
entity |
| Predicate | finalStronghold |
P89841
|
FINISHED |
| Object | Tenmokuzan |
—
|
NE NERFINISHED |
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: Tenmokuzan | Statement: [Takeda Katsuyori, finalStronghold, Tenmokuzan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalStronghold Context triple: [Takeda Katsuyori, finalStronghold, Tenmokuzan]
-
A.
currentStronghold
Indicates that an entity currently serves as the primary base, fortress, or central stronghold for another entity.
-
B.
primaryStronghold
Indicates that one location serves as the main base, fortress, or central stronghold for an entity compared to its other sites.
-
C.
strongholdOf
Indicates that a location serves as a primary fortified base, center of power, or main stronghold for a particular entity.
-
D.
isLastMajorStrongholdOf
chosen
Indicates that a location serves as the final significant defensive or strategic base controlled by a particular entity.
-
E.
mountainStronghold
Indicates a location that serves as a fortified or defensible stronghold situated in mountainous terrain.
- 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_69ee9cfe16088190a3dddd68e3c7b1ea |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 27, 2026, 2:18 a.m.