Triple
T37186031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piazza Pancali |
E921322
|
entity |
| Predicate | nearbyHistoricPeriod |
P51816
|
FINISHED |
| Object | Greek antiquity (Temple of Apollo) |
—
|
LITERAL FINISHED |
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: Greek antiquity (Temple of Apollo) | Statement: [Piazza Pancali, nearbyHistoricPeriod, Greek antiquity (Temple of Apollo)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyHistoricPeriod Context triple: [Piazza Pancali, nearbyHistoricPeriod, Greek antiquity (Temple of Apollo)]
-
A.
hasNearbyHistoricPeriod
chosen
Indicates that one historic period occurs close in time or space to another historic period.
-
B.
nearbyHistoricalFunction
Indicates that one entity is located close to another entity that has or had a historical role, use, or function.
-
C.
hasNearbyHistoricalEvent
Indicates that a given entity is located close to the site where a specific historical event occurred.
-
D.
historicalServiceNear
Indicates that a historical service or event occurred in close spatial proximity to a specified location or entity.
-
E.
nearbyHistoricalServiceFor
Indicates that a historical service or facility is located close to a given reference entity or location.
- 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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
Created at: May 3, 2026, 4:15 p.m.