Triple
T28936875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stauropolis |
E730341
|
entity |
| Predicate | hasRuinsSharedWith |
P170150
|
FINISHED |
| Object | Aphrodisias |
—
|
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: Aphrodisias | Statement: [Stauropolis, hasRuinsSharedWith, Aphrodisias]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRuinsSharedWith Context triple: [Stauropolis, hasRuinsSharedWith, Aphrodisias]
-
A.
hasRuinsOn
Indicates that one location or object contains or is the site of ruins situated upon it.
-
B.
hasRuin
Indicates that one entity possesses, contains, or is associated with a ruin or ruined structure.
-
C.
hasSharedBorderHistoryWith
Indicates that two entities have a history of sharing a common border or boundary at some point in time.
-
D.
haveSharedInfrastructure
Indicates that two or more entities use or depend on the same underlying physical or virtual infrastructure resources.
-
E.
hasNumberOfChurchRuins
Indicates the quantity of church ruins associated with a given entity.
- F. None of above. chosen
Provenance (4 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f68b121eac81909e90416207bc1157 |
completed | May 2, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f68a160374819084d720985f800dfc |
completed | May 2, 2026, 11:34 p.m. |
Created at: April 28, 2026, 8:33 a.m.