Triple
T8041418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Maron |
E187448
|
entity |
| Predicate | associatedWith |
P37
|
FINISHED |
| Object | Apamea |
E282642
|
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: Apamea | Statement: [Saint Maron, associatedWith, Apamea]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Apamea Context triple: [Saint Maron, associatedWith, Apamea]
-
A.
Apamea
Apamea was an important ancient Hellenistic and Roman city in the region of Phrygia in Asia Minor, known as a commercial and strategic center.
-
B.
Ptolemaida
Ptolemaida is a city in northern Greece known for its significant lignite mines and power plants, making it an important center of the country’s energy production.
-
C.
Peraea
Peraea is a historical region east of the Jordan River that formed part of ancient Judea during the Second Temple period.
-
D.
Stratonicea
Stratonicea was an important Hellenistic city in ancient Caria, known for its impressive urban layout and later Roman-era developments in what is now southwestern Turkey.
-
E.
Apamea on the Orontes
chosen
Apamea on the Orontes was an important Hellenistic and Roman city in Syria, known as a cultural and commercial center of the Seleucid Empire.
- 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_69ca82b00cb48190b59a300f70e97bd7 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f1e98508190a29a7bb5055f8ba0 |
completed | March 31, 2026, 3:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc5706a4a881909758ea34cf5c0cf2 |
completed | March 31, 2026, 11:21 p.m. |
Created at: March 30, 2026, 5:23 p.m.