Triple
T18555382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baeterrae |
E453489
|
entity |
| Predicate | hasApproximateDistanceToCoast |
P15760
|
FINISHED |
| Object | about 10 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: about 10 km | Statement: [Baeterrae, hasApproximateDistanceToCoast, about 10 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateDistanceToCoast Context triple: [Baeterrae, hasApproximateDistanceToCoast, about 10 km]
-
A.
hasNearbyCoast
Indicates that one location is situated close to a coastline or seashore.
-
B.
distanceFromCoast
chosen
Indicates the measured spatial separation between a location and the nearest point on a coastline.
-
C.
hasCoastlineLengthApprox
Indicates an approximate measurement of the total length of an entity’s coastline.
-
D.
hasNearbyMarineFeature
Indicates that one entity is located close to a marine geographic feature associated with the other entity.
-
E.
stateOnNearestShore
Indicates that an entity is located on the shore that is geographically closest to another specified reference point or 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53806046481908efbbe6909b2c68b |
completed | April 19, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:38 a.m.