Triple
T28451367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subotiv |
E716588
|
entity |
| Predicate | distanceToChyhyryn |
P201603
|
FINISHED |
| Object | approximately 7–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: approximately 7–10 km | Statement: [Subotiv, distanceToChyhyryn, approximately 7–10 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToChyhyryn Context triple: [Subotiv, distanceToChyhyryn, approximately 7–10 km]
-
A.
distanceToChambéryKilometersApprox
Indicates an approximate distance, measured in kilometers, between a given entity and the location of Chambéry.
-
B.
distanceToLePuy-en-Velay
Indicates the spatial distance between a given entity and the location of Le Puy-en-Velay.
-
C.
distanceToSighnaghi
Indicates the spatial distance between a given entity or location and Sighnaghi.
-
D.
distanceToCherkessk
Indicates the spatial distance between a given entity and the location of Cherkessk.
-
E.
distanceToSévaré
Indicates the spatial distance between a given entity and the location Sévaré.
- 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_69efd6b76f8c8190a7ba908aca280942 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_6a000be59ad88190a6aa3a42c097796d |
completed | May 10, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_6a000ab6e9bc81908300b81d004e5921 |
completed | May 10, 2026, 4:33 a.m. |
| PDg | Predicate description generation | batch_6a000be4d3f48190bdecd0a044a0e453 |
completed | May 10, 2026, 4:39 a.m. |
Created at: April 28, 2026, 1:52 a.m.