Triple
T26340649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gokishichidō system |
E662636
|
entity |
| Predicate | regionalCircuitsCalled |
P178264
|
FINISHED |
| Object | shichi-dō |
—
|
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: shichi-dō | Statement: [Gokishichidō system, regionalCircuitsCalled, shichi-dō]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionalCircuitsCalled Context triple: [Gokishichidō system, regionalCircuitsCalled, shichi-dō]
-
A.
numberOfCircuits
Indicates the total count of circuits associated with or contained in a given entity or system.
-
B.
numberOfRegionalCourts
Indicates the total count of regional courts associated with a given entity.
-
C.
regionalsNumber
Indicates the number of regional-level instances (such as events, competitions, or units) associated with an entity.
-
D.
territorialCall
Indicates a vocalization used by an entity to mark, defend, or assert control over a territory against others.
-
E.
regionNumber
Indicates that an entity is assigned to or associated with a specific numbered region within a larger spatial or organizational division.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: April 26, 2026, 10:38 p.m.