Triple
T38519489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laodicea |
E922432
|
entity |
| Predicate | modernSiteKnownAs |
P88073
|
FINISHED |
| Object | Laodicea on the Lycus |
—
|
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: Laodicea on the Lycus | Statement: [Laodicea, modernSiteKnownAs, Laodicea on the Lycus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernSiteKnownAs Context triple: [Laodicea, modernSiteKnownAs, Laodicea on the Lycus]
-
A.
modernSiteCorrespondsTo
chosen
Indicates that a present-day site occupies, aligns with, or directly relates to the location or extent of another (typically historical or earlier) site.
-
B.
historicalNameOfSite
Indicates that one name is a former or past name historically used for a given site or location.
-
C.
formerSiteOf
Indicates that a location previously hosted or contained something (such as a structure, organization, or event) that is no longer present there.
-
D.
laterBecameKnownAs
Indicates that an entity was previously known by one name or identity and, at a later time, came to be known by a different name or identity.
-
E.
formerlyKnownLocationAs
Indicates that an entity was previously known or referred to by a different location name or designation.
- 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_69f76ea5f5588190bd0b28c82e975640 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
Created at: May 3, 2026, 4:32 p.m.