Triple
T27823540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 洪秀柱 |
E702884
|
entity |
| Predicate | residence |
P75
|
FINISHED |
| Object |
臺灣新北市
臺灣新北市是位於臺灣北部、環繞臺北市的直轄市,也是全臺人口最多且都市與山海景觀並存的重要都會區。
|
E1792541
|
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: 臺灣新北市 | Statement: [洪秀柱, residence, 臺灣新北市]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: 臺灣新北市 Triple: [洪秀柱, residence, 臺灣新北市]
Generated description
臺灣新北市是位於臺灣北部、環繞臺北市的直轄市,也是全臺人口最多且都市與山海景觀並存的重要都會區。
Provenance (5 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_69ef840ad1e88190b5bff2d1ddec8700 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6386fd3c881908bd96b538619cd0f |
completed | May 2, 2026, 5:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a12f72842f08190a1c2e811c68ec2ca |
completed | May 24, 2026, 1:03 p.m. |
| NEDg | Description generation | batch_6a12fb4a4a808190bc0821b2bc754da0 |
completed | May 24, 2026, 1:21 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a12fd21fb2c8190b52459bd901c05a0 |
completed | May 24, 2026, 1:29 p.m. |
Created at: April 27, 2026, 5:50 p.m.