Triple
T15660303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keelung |
E376549
|
entity |
| Predicate | hasName |
P744
|
FINISHED |
| Object | Chilung |
E376549
|
NE 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: Chilung | Statement: [Keelung, hasName, Chilung]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chilung Context triple: [Keelung, hasName, Chilung]
-
A.
Chilung
chosen
Chilung is an alternative romanization of Keelung, a major port city in northern Taiwan known for its harbor and night market.
-
B.
Tillangchong
Tillangchong is a remote, sparsely inhabited island in India’s Nicobar archipelago, noted for its dense tropical forests and rich marine and bird life.
-
C.
Chuping
Chuping is a town in the Malaysian state of Perlis, known for its extensive sugarcane plantations and hot climate.
-
D.
Chang Naga
Chang Naga are an indigenous Naga ethnic group of northeastern India, known for their distinct language, traditional warrior culture, and rich ceremonial practices.
-
E.
Phungling
Phungling is a town in eastern Nepal that serves as the main urban and commercial center of Taplejung District in Province No. 1.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ef4e6a08190ad8bbafaa3612f22 |
completed | April 16, 2026, 2:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff6ed6f50c81909d87ced263064f0d |
completed | May 9, 2026, 5:28 p.m. |
Created at: April 10, 2026, 4:15 a.m.