Triple
T35766895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hachinohe |
E1034040
|
entity |
| Predicate | isCoreCitySince |
P183648
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [Hachinohe, isCoreCitySince, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCoreCitySince Context triple: [Hachinohe, isCoreCitySince, 2001]
-
A.
isCoreCity
Indicates that a city serves as a primary, central, or most important urban area within a larger region, system, or network.
-
B.
isMetropolitanCoreOf
Indicates that one area functions as the central, most urbanized core within a larger metropolitan region or system.
-
C.
isMetropolitanCitySince
Indicates that an entity has held the status of a metropolitan city starting from a specified point in time.
-
D.
hasCurrentCoreCityName
Indicates that an entity is associated with its present or officially recognized core city name.
-
E.
hasCoreTown
Indicates that an entity possesses or is associated with a primary or central town that serves as its main urban center.
- 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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a1f64f1081908cc2774840684310 |
completed | May 3, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a162672481909773f8383d91159a |
completed | May 3, 2026, 7:26 p.m. |
Created at: May 3, 2026, 4:06 p.m.