Triple
T17624995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timavo River |
E429816
|
entity |
| Predicate | hasUndergroundCourse |
P128319
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Timavo River, hasUndergroundCourse, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUndergroundCourse Context triple: [Timavo River, hasUndergroundCourse, true]
-
A.
hasTypicalCourse
Indicates that there is a characteristic or commonly observed progression, sequence, or development pattern associated with the subject.
-
B.
hasPrimaryCourse
Indicates that an entity is associated with its main or principal course in a given context (such as a meal, curriculum, or sequence of offerings).
-
C.
hasHostCourse
Indicates that one entity serves as the primary or organizing course responsible for hosting or containing another related course or course component.
-
D.
hasPar3Course
Indicates that an entity (such as a golf facility or location) includes or is associated with a par-3 golf course.
-
E.
hasMultipleCourses
Indicates that an entity is associated with more than one course within the given context.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46dbb2a348190982658d495c81da0 |
completed | April 19, 2026, 5:52 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 5:52 a.m.