Triple
T25908263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zenne River |
E652815
|
entity |
| Predicate | hasHiddenCourseIn |
P128319
|
FINISHED |
| Object | Brussels |
—
|
NE NERFINISHED |
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: Brussels | Statement: [Zenne River, hasHiddenCourseIn, Brussels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHiddenCourseIn Context triple: [Zenne River, hasHiddenCourseIn, Brussels]
-
A.
hasHostCourse
Indicates that one entity serves as the primary or organizing course responsible for hosting or containing another related course or course component.
-
B.
hasUndergroundCourse
chosen
Indicates that one entity includes or is associated with a course or passage that runs underground.
-
C.
hasStructureOnCourse
Indicates that a physical structure is located on, along, or directly associated with a specific course or route.
-
D.
hasParCourse
Indicates that an entity is associated with, or includes, a specific par course (an exercise or fitness trail with designated stations).
-
E.
hasSisterCourse
Indicates that one course is related to another as a sister course, typically sharing similar content, level, or structure within the same curriculum or program.
- 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_69e7ab3d3f8481909bc53ed64c06af33 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 22, 2026, 8:27 a.m.