Triple
T37058993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selinunte |
E917268
|
entity |
| Predicate | nearbyQuarry |
P176629
|
FINISHED |
| Object | Cave di Cusa |
—
|
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: Cave di Cusa | Statement: [Selinunte, nearbyQuarry, Cave di Cusa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyQuarry Context triple: [Selinunte, nearbyQuarry, Cave di Cusa]
-
A.
quarriedNear
Indicates that a material or resource was extracted from a quarry located close to a specified place or feature.
-
B.
quarrySource
chosen
Indicates that one entity serves as the extraction site or origin location from which another entity (typically a material or resource) is quarried.
-
C.
quarryRegion
Indicates that a specified region is the location where quarrying or extraction activities take place.
-
D.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
E.
nearbyFrontier
Indicates that one entity is located close to a boundary or frontier region associated with 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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff0214d7348190904688376df99bce |
completed | May 9, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69feffd62fec8190a855922c8b3c57cf |
completed | May 9, 2026, 9:35 a.m. |
Created at: May 3, 2026, 4:14 p.m.