Triple
T24303249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ōuchi clan |
E612457
|
entity |
| Predicate | capitalCityUnderControl |
P151561
|
FINISHED |
| Object | Yamaguchi |
—
|
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: Yamaguchi | Statement: [Ōuchi clan, capitalCityUnderControl, Yamaguchi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalCityUnderControl Context triple: [Ōuchi clan, capitalCityUnderControl, Yamaguchi]
-
A.
capitalCityInvolved
Indicates that a capital city participates in, is affected by, or plays a role in a specified event, process, or relationship.
-
B.
capitalOfLeadingSide
Indicates that one entity is the capital city or primary administrative center of the leading or principal side in a conflict, negotiation, or competitive relationship.
-
C.
capitalOfProvinceCaptured
Indicates that a particular force or entity has taken control of the capital city of a specified province.
-
D.
capitalCityGoverningFrom
chosen
Indicates that a specified capital city serves as the administrative center from which a given political entity is governed.
-
E.
cityOwned
Indicates that something is owned, managed, or under the jurisdiction of a city or municipal government.
- 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292239aa88190847e78ffd31eab4e |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:28 a.m.