Triple
T24613439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mōri clan |
E609181
|
entity |
| Predicate | laterDomainCenter |
P156752
|
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: [Mōri clan, laterDomainCenter, Yamaguchi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterDomainCenter Context triple: [Mōri clan, laterDomainCenter, Yamaguchi]
-
A.
laterDomain
Indicates that one domain or time interval occurs strictly after another in a temporal ordering.
-
B.
domainServed
Indicates that a particular domain or area is supported, covered, or provided for by a given entity or service.
-
C.
publicDomain
Indicates that a work or resource is not protected by intellectual property rights and is freely available for anyone to use, copy, modify, and distribute without restriction.
-
D.
secondaryDomain
Indicates that one domain functions as a secondary or auxiliary domain in relation to a primary domain.
-
E.
partOfDomain
Indicates that one entity belongs to, is included within, or is a constituent part of the scope or domain defined by another entity.
- 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_69e2c4d1140081909c58667bf68f80c3 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:31 a.m.