Triple
T4145029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herculaneum |
E89360
|
entity |
| Predicate | distanceFromVesuvius |
P54137
|
FINISHED |
| Object | approximately 7 km |
—
|
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: approximately 7 km | Statement: [Herculaneum, distanceFromVesuvius, approximately 7 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromVesuvius Context triple: [Herculaneum, distanceFromVesuvius, approximately 7 km]
-
A.
nearVolcano
Indicates that one entity is located in close proximity to a volcano.
-
B.
distanceFromHypocenter
Indicates the measured distance between a specified location and the hypocenter (origin point) of an event such as an earthquake.
-
C.
associatedVolcano
Indicates that there is a specific volcano linked or connected to the referenced entity, such as by location, impact, or relevance.
-
D.
distanceFromRome
Indicates the measured spatial distance between a given entity’s location and the city of Rome.
-
E.
isVolcanicNeighborOf
Indicates that one geographic feature is located close enough to another volcanic feature that they are considered neighboring volcano-related entities.
- 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_69aed95785788190ae75bcf0cd1cafdf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af018a54848190987f18c066c75068 |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af039fb19c8190b20e62a3b3ad25c1 |
completed | March 9, 2026, 5:30 p.m. |
Created at: March 9, 2026, 3:43 p.m.