Triple
T25360419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cremera River |
E635944
|
entity |
| Predicate | nearbyAncientSettlement |
P55312
|
FINISHED |
| Object | Veii |
—
|
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: Veii | Statement: [Cremera River, nearbyAncientSettlement, Veii]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyAncientSettlement Context triple: [Cremera River, nearbyAncientSettlement, Veii]
-
A.
nearbyArchaeologicalCulture
Indicates that one archaeological culture is geographically close to another archaeological culture.
-
B.
nearbyRomanTown
Indicates that one location is geographically close to a town that existed during the Roman period.
-
C.
nearbySettlements
Indicates that one settlement is located close to another settlement in geographic space.
-
D.
nearAncientRegion
Indicates that one entity is located close to, or in the immediate vicinity of, a specified ancient geographical region.
-
E.
hasNearbyAncientCity
chosen
Indicates that one entity is located close to another entity that is classified as an ancient city.
- 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 21, 2026, 1:36 p.m.