Triple
T24426535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hazebrouck |
E615874
|
entity |
| Predicate | regionCapitalDistanceKm |
P122332
|
FINISHED |
| Object | about 40 |
—
|
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 40 | Statement: [Hazebrouck, regionCapitalDistanceKm, about 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionCapitalDistanceKm Context triple: [Hazebrouck, regionCapitalDistanceKm, about 40]
-
A.
distanceFromCapital
Indicates the measured distance between a given location and the capital city of its corresponding region or country.
-
B.
regionCapitalDistanceRelation
Indicates a relationship specifying the distance between a region and its capital.
-
C.
distanceFromRegionalCapital
chosen
Indicates the measured spatial distance between a given place and its corresponding regional capital.
-
D.
distanceToProvinceCapital_km
Indicates the distance, measured in kilometers, between a given location and the capital city of its province.
-
E.
prefecturalCapitalDistanceRelation
Indicates a spatial relationship specifying the distance between an entity and the capital city of its prefecture.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a7406481908b85f3befc8feeee |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:15 a.m.