Triple
T30584791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Musashi Province |
E778474
|
entity |
| Predicate | oldProvinceCode |
P99880
|
FINISHED |
| Object | Musashi |
—
|
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: Musashi | Statement: [Musashi Province, oldProvinceCode, Musashi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oldProvinceCode Context triple: [Musashi Province, oldProvinceCode, Musashi]
-
A.
previousProvince
Indicates that one province was the immediately preceding administrative region of another in a temporal or historical sequence.
-
B.
formerNameOfProvince
Indicates that one name was previously used as the official name of a province before being replaced by another name.
-
C.
formerProvince
Indicates that an entity was previously a province of another entity but no longer holds that administrative status.
-
D.
baseProvince
Indicates that one administrative or territorial unit serves as the primary or originating province associated with another entity.
-
E.
hasProvincialCode
chosen
Indicates that an entity is associated with a specific provincial code that identifies its province or administrative region.
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689462ab48190b9b3bfff9ef1a5bc |
completed | May 2, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:23 p.m.