Triple
T836169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicomedia |
E18072
|
entity |
| Predicate | locatedDistanceFrom |
P7750
|
FINISHED |
| Object | about 100 km east of Constantinople |
—
|
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 100 km east of Constantinople | Statement: [Nicomedia, locatedDistanceFrom, about 100 km east of Constantinople]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedDistanceFrom Context triple: [Nicomedia, locatedDistanceFrom, about 100 km east of Constantinople]
-
A.
distanceCharacteristic
Indicates a relationship where an entity is described or constrained by some property or measure of distance (e.g., range, spacing, or separation).
-
B.
distanceFromTerminus
Indicates the measured distance of an entity from a defined endpoint or terminus along a route, path, or sequence.
-
C.
distance
chosen
Indicates the spatial separation or length between two points, objects, or locations.
-
D.
flightDistance
Indicates the measured distance covered by a flight between its origin and destination.
-
E.
distanceFromDowntown
Indicates the physical distance between a given location and the central downtown area.
- 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_69a49389f44881909a608fb27d89f247 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abce08348190b716e3ce5a638f99 |
completed | March 1, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7c7df881909c539c3ab8ff0367 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.