Triple
T4838978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rashbi |
E108131
|
entity |
| Predicate | burialPlace |
P196
|
FINISHED |
| Object | Meron |
E104864
|
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: Meron | Statement: [Rashbi, burialPlace, Meron]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Meron Context triple: [Rashbi, burialPlace, Meron]
-
A.
Hamra
Hamra is a vibrant, cosmopolitan neighborhood in Beirut, Lebanon, known for its bustling commercial streets, cafes, and cultural life.
-
B.
Mount Meron
chosen
Mount Meron is a prominent mountain in northern Israel known for its religious significance, nature reserves, and status as one of the country's highest peaks.
-
C.
Ḥimṣ
Ḥimṣ is an alternative transliteration of Homs, a major city in western Syria known for its historical significance and role in the Syrian conflict.
-
D.
Talagante
Talagante is a commune and town in central Chile, located southwest of Santiago within the Santiago Metropolitan Region.
-
E.
Emesa
Emesa is the ancient name of the Syrian city now known as Homs, historically significant as a religious and trading center in Roman and early Christian times.
- 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ce4a5108190aede620d5dde1f81 |
completed | March 20, 2026, 3:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be5cc5861881908ad3838168325a34 |
completed | March 21, 2026, 8:54 a.m. |
Created at: March 20, 2026, 1:25 p.m.