Triple
T37934732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andromachus of Tauromenium |
E946314
|
entity |
| Predicate | modernLocationOfFoundedCity |
P155515
|
FINISHED |
| Object | Taormina |
—
|
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: Taormina | Statement: [Andromachus of Tauromenium, modernLocationOfFoundedCity, Taormina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernLocationOfFoundedCity Context triple: [Andromachus of Tauromenium, modernLocationOfFoundedCity, Taormina]
-
A.
modernLocationOfCity
chosen
Indicates that a historical or former city is located within the boundaries of a specified modern administrative or geographic entity.
-
B.
majorCityFounded
Indicates that one entity is a major city and the other is the date or event of its founding.
-
C.
foundedCityOnSiteOf
Indicates that a city was established on the same physical location where another settlement or city previously existed.
-
D.
cityFounded
Indicates that a particular city was established or came into existence at a specific time or by a specific founding event or agent.
-
E.
nearbyCityFoundedBy
Indicates that a city was founded by an entity (such as a person, group, or organization) that is located near that city.
- F. None of above.
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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.