Triple
T5571514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sado, Niigata, Japan |
E146212
|
entity |
| Predicate | mergedAsCityOn |
P306
|
FINISHED |
| Object | 2004-03-01 |
—
|
LITERAL FINISHED |
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: 2004-03-01 | Statement: [Sado, Niigata, Japan, mergedAsCityOn, 2004-03-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergedAsCityOn Context triple: [Sado, Niigata, Japan, mergedAsCityOn, 2004-03-01]
-
A.
formerMunicipalityOf
Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
-
B.
acquiredByCity
Indicates that something (such as property, assets, or an organization) has been obtained or taken ownership of by a city.
-
C.
previouslyContainedCity
Indicates that one location used to include a particular city within its boundaries or jurisdiction at some time in the past, but no longer does.
-
D.
incorporatedAsCity
chosen
Indicates that an entity was formally established and legally recognized as a city.
-
E.
hasAssociatedCityFormerName
Indicates that an entity is linked to a city by referencing one of that city's former or historical names.
- 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_69c008ffed108190a084602227af6157 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020502a288190af37f9ebb88fccae |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b147cc081909237f3f2967d4cb8 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:37 p.m.