Triple
T21607799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kong Lin |
E533222
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Qufu |
—
|
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: Qufu | Statement: [Kong Lin, locatedIn, Qufu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Qufu Context triple: [Kong Lin, locatedIn, Qufu]
-
A.
Qufu
chosen
Qufu is an ancient city in eastern China renowned as the birthplace of Confucius and a major center of Confucian heritage.
-
B.
Zoucheng
Zoucheng is a county-level city in Shandong Province, China, historically known as the hometown of the ancient philosopher Mencius.
-
C.
Jining
Jining is a city in Shandong Province, China, historically significant as a transport and commercial hub along the Grand Canal.
-
D.
Jinan
Jinan is the capital city of Shandong Province in eastern China, known for its numerous natural springs and rich historical and cultural heritage.
-
E.
Yanzhou
Yanzhou is an ancient historical region in what is now western Shandong, China, known as one of the traditional Nine Provinces of early Chinese civilization.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c46411108190bba0d4176dffc9f3 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef17e6378881908678dc903b8ba6ac |
completed | April 27, 2026, 8:01 a.m. |
Created at: April 16, 2026, 6:33 p.m.