Triple
T15922449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mur de Huy |
E386124
|
entity |
| Predicate | cityAccess |
P120553
|
FINISHED |
| Object | connects lower Huy to upper Huy |
—
|
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: connects lower Huy to upper Huy | Statement: [Mur de Huy, cityAccess, connects lower Huy to upper Huy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityAccess Context triple: [Mur de Huy, cityAccess, connects lower Huy to upper Huy]
-
A.
cityCentreAccess
Indicates whether an entity has access to, or is reachable within, the central area of a city.
-
B.
cityService
Indicates that a service is provided by, operates within, or is administered by a particular city.
-
C.
cityGateTo
Indicates a directional relationship where one location or path leads to or opens into a city gate.
-
D.
cityFunction
Indicates the primary role, purpose, or functional classification associated with a city (e.g., administrative, commercial, industrial, cultural).
-
E.
tourAccess
Indicates that an entity is permitted to participate in, enter, or make use of a specific tour.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69e172b213e481909ee0c05e16229a26 |
completed | April 16, 2026, 11:37 p.m. |
Created at: April 10, 2026, 4:52 a.m.