Triple
T38027879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamana clan |
E948828
|
entity |
| Predicate | supportedSideInNanbokuCho |
P207563
|
FINISHED |
| Object | Southern Court |
E957290
|
NE 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: Southern Court | Statement: [Yamana clan, supportedSideInNanbokuCho, Southern Court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedSideInNanbokuCho Context triple: [Yamana clan, supportedSideInNanbokuCho, Southern Court]
-
A.
sideInBattleOfSekigahara
Indicates that an entity participated as a side or faction in the Battle of Sekigahara.
-
B.
usesKakaliNishada
Indicates that one entity employs or incorporates the specific musical element or note known as Kakali Nishada in relation to another entity or context.
-
C.
usedUnderShogun
Indicates that something was utilized or operated under the authority, control, or governance of a shogun.
-
D.
ichinomiya
Indicates a relationship where a location or institution holds the status of "Ichinomiya," the primary or highest-ranking Shinto shrine of a historical province.
-
E.
hasMidoriNoMadoguchi
Indicates that an entity (typically a train station) is equipped with a "Midori no Madoguchi" staffed ticket office or service counter.
- F. None of above. chosen
Provenance (5 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_69f76efd1bc48190a729097fe5177b61 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a417b1b823c8190b83ef25a5dd20f72 |
completed | June 28, 2026, 7:50 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037df009f4819082e04683e6e8a106 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:20 p.m.