Triple
T28710082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollonia Archaeological Museum |
E729806
|
entity |
| Predicate | locatedWithinSite |
P40
|
FINISHED |
| Object | Apollonia archaeological park |
—
|
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: Apollonia archaeological park | Statement: [Apollonia Archaeological Museum, locatedWithinSite, Apollonia archaeological park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedWithinSite Context triple: [Apollonia Archaeological Museum, locatedWithinSite, Apollonia archaeological park]
-
A.
isOnSiteWith
Indicates that two or more entities are physically present at the same site or location at the same time.
-
B.
containsSite
Indicates that one entity spatially or structurally includes another entity as a site or location within its bounds.
-
C.
isSiteOf
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
D.
locatedWith
Indicates that two or more entities are situated together in the same place or spatial context.
-
E.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69ff9a25407c81909faa86e72a7a9d17 |
completed | May 9, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69ff99c613688190a03b2f93d5ccad2b |
completed | May 9, 2026, 8:32 p.m. |
Created at: April 28, 2026, 5:47 a.m.