Triple
T25096123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 熊本市 |
E628592
|
entity |
| Predicate | 著名な武将との関係 |
P157640
|
FINISHED |
| Object | 加藤清正が築城した熊本城の城下町 |
—
|
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: 加藤清正が築城した熊本城の城下町 | Statement: [熊本市, 著名な武将との関係, 加藤清正が築城した熊本城の城下町]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 著名な武将との関係 Context triple: [熊本市, 著名な武将との関係, 加藤清正が築城した熊本城の城下町]
-
A.
notableCommanderOrAlly
Indicates that an entity is a significant military leader or important ally associated with another entity, such as a person, group, or organization.
-
B.
notableCommanderAtAction
Indicates that a particular commander is notably associated with leading or playing a significant command role in a specific action or event.
-
C.
notableCombatant
Indicates that an entity is recognized as a significant or distinguished participant in a particular conflict or combat event.
-
D.
notableCommanderOf
Indicates that an individual is a distinguished or historically significant commander associated with leading a particular military unit, force, or organization.
-
E.
associatedWithBattle
Indicates a relationship where an entity is connected or linked to a specific battle, such as by participation, relevance, or involvement.
- F. None of above. chosen
Provenance (4 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f464b9651481908d4d7584717f5c59 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:25 a.m.