Triple
T27017261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verbanesi |
E680567
|
entity |
| Predicate | associatedWithLakeActivities |
P106010
|
FINISHED |
| Object | boating |
—
|
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: boating | Statement: [Verbanesi, associatedWithLakeActivities, boating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithLakeActivities Context triple: [Verbanesi, associatedWithLakeActivities, boating]
-
A.
usesLakeFor
Indicates that an entity utilizes a lake as a resource or setting for some purpose, activity, or function.
-
B.
connectsToByLake
Indicates that one entity is linked or joined to another specifically via a lake as the connecting medium or route.
-
C.
hasWaterRelatedActivity
chosen
Indicates that an entity engages in, offers, or is associated with an activity involving water (e.g., swimming, boating, or other water-based actions).
-
D.
recreationActivitiesSupported
Indicates that an entity provides, allows, or is compatible with certain recreational activities.
-
E.
associatedWithNationalPark
Indicates a relationship in which an entity has a connection or linkage to a specific national park, such as location, administration, or relevant activity.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff9d9cb4f8819083682be3c483b599 |
completed | May 9, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69ff9c38bf9c8190bbb85b32f3ae3d2e |
completed | May 9, 2026, 8:42 p.m. |
Created at: April 27, 2026, 7:06 a.m.