Triple
T35479489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tosa |
E1025428
|
entity |
| Predicate | domainNameInEdoPeriod |
P156751
|
FINISHED |
| Object | Tosa Domain |
—
|
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: Tosa Domain | Statement: [Tosa, domainNameInEdoPeriod, Tosa Domain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domainNameInEdoPeriod Context triple: [Tosa, domainNameInEdoPeriod, Tosa Domain]
-
A.
mainEdoPeriodDomain
chosen
Indicates that the subject is the primary territorial or domainal holding associated with the entity during the Edo period.
-
B.
duringEdoPeriod
Indicates that an event, action, or state occurred within the historical timeframe of the Edo period.
-
C.
endOfEdoPeriod
Indicates that an event, state, or condition occurs at or marks the conclusion of the Edo period.
-
D.
roleInEdoPeriod
Indicates that an entity held a specific role, position, or function during Japan’s Edo period.
-
E.
startOfEdoPeriod
Indicates that something marks the beginning or initial phase of the Edo period in Japanese history.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.