Triple
T34321020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ouchi-juku |
E880734
|
entity |
| Predicate | connectedDomain |
P199711
|
FINISHED |
| Object | Aizu-Wakamatsu |
—
|
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: Aizu-Wakamatsu | Statement: [Ouchi-juku, connectedDomain, Aizu-Wakamatsu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedDomain Context triple: [Ouchi-juku, connectedDomain, Aizu-Wakamatsu]
-
A.
involvedDomain
Indicates that an entity participates in or is associated with a particular domain, field, or area of activity.
-
B.
recognizedAsDomain
Indicates that one entity is acknowledged or accepted as a valid or authoritative domain associated with another entity.
-
C.
inputDomain
Indicates that a function, process, or system accepts inputs belonging to a specified domain or set of allowable values.
-
D.
affectedDomain
Indicates the domain, field, or area that is impacted or influenced by a given action, event, or condition.
-
E.
containsDomain
Indicates that one entity includes or encompasses a specific domain as part of its scope, structure, or area of applicability.
- 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_69f349b9cd508190a996a616903b3e6d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff519b65f081909902ba83b775ef85 |
completed | May 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69ff506fccdc8190bd93269589040aed |
completed | May 9, 2026, 3:19 p.m. |
| PDg | Predicate description generation | batch_69ff519a67008190b1eda931fdeff53e |
completed | May 9, 2026, 3:24 p.m. |
Created at: May 1, 2026, 1:57 a.m.