Triple
T14527447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Li Shang |
E340815
|
entity |
| Predicate | allyOf |
P4662
|
FINISHED |
| Object | Ling |
E634575
|
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: Ling | Statement: [Li Shang, allyOf, Ling]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ling Context triple: [Li Shang, allyOf, Ling]
-
A.
Ling
chosen
Ling is a Chinese-origin surname shared by numerous individuals worldwide, including prominent figures in media, politics, and academia.
-
B.
Lingg
Lingg is a German surname most notably associated with Louis Lingg, one of the anarchists linked to the 1886 Haymarket affair in Chicago.
-
C.
Lingig
Lingig is a coastal municipality in the province of Surigao del Sur in the Philippines, known for its fishing communities and rural landscapes.
-
D.
Linge
Linge is a river in the Netherlands known for flowing through the Betuwe region and its picturesque orchards and villages.
-
E.
Lingling
Lingling is an ancient Chinese city and former administrative region whose name historically referred to what is now Yongzhou in Hunan Province.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea051bc608190ad4d516c5e7bca43 |
completed | April 14, 2026, 8:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd7a52260881909a0d85603666107d |
completed | May 8, 2026, 5:53 a.m. |
Created at: April 10, 2026, 1:22 a.m.