Triple
T26396687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Csorna |
E663579
|
entity |
| Predicate | distanceToSopron_km |
P196204
|
FINISHED |
| Object | about 50 |
—
|
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 50 | Statement: [Csorna, distanceToSopron_km, about 50]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToSopron_km Context triple: [Csorna, distanceToSopron_km, about 50]
-
A.
distanceToBudapest_km
Indicates the physical distance, measured in kilometers, between a given location and Budapest.
-
B.
distanceToGyőr_km
Indicates the physical distance, measured in kilometers, between an entity and the city of Győr.
-
C.
distanceToKecskemét_km
Indicates the physical distance, measured in kilometers, from a given location to Kecskemét.
-
D.
distanceToSzeged_km
Indicates the physical distance, measured in kilometers, between an entity and the city of Szeged.
-
E.
distanceFromBratislava_km
Indicates the distance, measured in kilometers, between a given entity’s location and the city of Bratislava.
- 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
| PDg | Predicate description generation | batch_69fe1639613c8190aaf1b4c8e2d861ba |
completed | May 8, 2026, 4:58 p.m. |
Created at: April 26, 2026, 11:29 p.m.