Triple
T10817355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harkhuf |
E255265
|
entity |
| Predicate | regionExplored |
P1562
|
FINISHED |
| Object | Yam |
E196863
|
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: Yam | Statement: [Harkhuf, regionExplored, Yam]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yam Context triple: [Harkhuf, regionExplored, Yam]
-
A.
Yam
chosen
Yam is the ancient Canaanite and Phoenician god of the sea, often depicted as a primordial chaos deity and rival of the storm god Baal.
-
B.
Yam
Yam is a Cantonese romanization of the Chinese surname Yan, commonly used among Cantonese-speaking communities.
-
C.
Yam O
Yam O is an area on Lantau Island in Hong Kong, known for its coastal location near major infrastructure such as Penny’s Bay and the Hong Kong–Zhuhai–Macao Bridge link roads.
-
D.
Taro
Taro is a common Japanese male given name, often written with kanji meaning "eldest son" or similar traditional connotations.
-
E.
Taro
The Taro is a river in northern Italy that flows through the Emilia-Romagna region and ultimately joins the Po River.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d733eea03c8190a68f4d4f89f497a2 |
completed | April 9, 2026, 5:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69deb0f9e3a081908163b398d845deeb |
completed | April 14, 2026, 9:26 p.m. |
Created at: April 8, 2026, 9:18 p.m.