Triple
T21865669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Paul |
E539876
|
entity |
| Predicate | associatedWith |
P37
|
FINISHED |
| Object | Tarsus |
—
|
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: Tarsus | Statement: [Saint Paul, associatedWith, Tarsus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tarsus Context triple: [Saint Paul, associatedWith, Tarsus]
-
A.
Tarsus
chosen
Tarsus is an ancient city in Cilicia (in modern-day Turkey) known as a major cultural and commercial center of the Roman Empire and as the birthplace of the Apostle Paul.
-
B.
Smyrna
Smyrna was a major Aegean port city (modern-day İzmir in Turkey) that served as a key commercial and cultural hub in the Ottoman Empire.
-
C.
Smyrna
Smyrna is a suburban city in the Atlanta metropolitan area known for its residential communities, parks, and proximity to major Atlanta attractions.
-
D.
Smyrna
Smyrna is a small unincorporated community located within Greenwood County in the U.S. state of Kansas.
-
E.
Smyrna
Smyrna is a small historic town in central Delaware known for its colonial-era roots and location along major transportation routes.
- 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0d63f2ec48190956a3e99d8f98b1f |
completed | April 28, 2026, 3:46 p.m. |
Created at: April 16, 2026, 6:56 p.m.