Triple
T25848955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kavalan people |
E651147
|
entity |
| Predicate | currentSettlement |
P171391
|
FINISHED |
| Object | Hualien County |
—
|
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: Hualien County | Statement: [Kavalan people, currentSettlement, Hualien County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentSettlement Context triple: [Kavalan people, currentSettlement, Hualien County]
-
A.
currentSettlementType
Indicates the specific category or classification of settlement (such as village, town, or city) that currently applies to an entity.
-
B.
settlementState
Indicates the state or status of a settlement process or transaction at a given point in time.
-
C.
isSettlement
Indicates that the subject entity functions as a human-inhabited place or community, such as a town, village, or city.
-
D.
hasSettlementAround
Indicates that a settlement is located in the surrounding area of a specified place or feature.
-
E.
settlementWith
Indicates a relationship where one party reaches or maintains a settlement or agreement with another party, typically resolving a dispute or claim.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 22, 2026, 7:57 a.m.