Triple
T31325377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sibari |
E798868
|
entity |
| Predicate | hasNearbyAncientSettlement |
P55312
|
FINISHED |
| Object | Sybaris |
—
|
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: Sybaris | Statement: [Sibari, hasNearbyAncientSettlement, Sybaris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyAncientSettlement Context triple: [Sibari, hasNearbyAncientSettlement, Sybaris]
-
A.
hasNearbyAncientCity
chosen
Indicates that one entity is located close to another entity that is classified as an ancient city.
-
B.
hasNearbyAncientCulture
Indicates that one entity is geographically close to another entity associated with an ancient culture or civilization.
-
C.
hasNearbyArchaeologicalSite
Indicates that an entity is located close to or in the vicinity of an archaeological site.
-
D.
hasAncientColony
Indicates that an entity established or possessed a colony in ancient times.
-
E.
locatedInOrNearModernSettlement
Indicates that something is situated within or in close proximity to a present-day town, city, or other populated settlement.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fee335cb08819097e3a0e09d5ebf49 |
completed | May 9, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69fee2c74fd88190acfc045ab07b7f6b |
completed | May 9, 2026, 7:31 a.m. |
Created at: April 29, 2026, 9:15 p.m.