Triple
T26371525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 奉化区 |
E660784
|
entity |
| Predicate | historicalTownWithin |
P43430
|
FINISHED |
| Object | 溪口镇 |
—
|
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: 溪口镇 | Statement: [奉化区, historicalTownWithin, 溪口镇]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalTownWithin Context triple: [奉化区, historicalTownWithin, 溪口镇]
-
A.
containsHistoricTown
chosen
Indicates that one entity geographically includes or encompasses a town that has recognized historical significance.
-
B.
historicalMainTown
Indicates that one place served as the primary or principal town for another place during a specific historical period.
-
C.
historicalTownName
Indicates that the object is a former or historical name by which the town (subject) was previously known.
-
D.
governsHistoricTown
Indicates that one entity exercises official governing authority over a town that is recognized as historically significant.
-
E.
historicalTownshipOf
Indicates that one entity was formerly a township encompassing or governing the other entity during a past historical period.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 26, 2026, 10:58 p.m.