Triple
T36641381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiberius Julius Celsus Polemaeanus |
E904594
|
entity |
| Predicate | honorificMonumentLocation |
P96634
|
FINISHED |
| Object | Ephesus, Asia Minor |
—
|
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: Ephesus, Asia Minor | Statement: [Tiberius Julius Celsus Polemaeanus, honorificMonumentLocation, Ephesus, Asia Minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificMonumentLocation Context triple: [Tiberius Julius Celsus Polemaeanus, honorificMonumentLocation, Ephesus, Asia Minor]
-
A.
monumentsLocation
chosen
Indicates the geographical place where a monument is situated or located.
-
B.
memorialLocatedAt
Indicates that a memorial is situated or found at a specific location.
-
C.
restingPlaceOf
Indicates the location where an entity is laid to rest, stored, or kept, typically as its final or usual resting location.
-
D.
monumentName
Indicates the specific name assigned to a monument associated with an entity.
-
E.
memorialSiteFor
Indicates that a place or structure serves as a dedicated site of remembrance or commemoration for a particular person, group, or event.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:11 p.m.