Triple
T12884765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Floss |
E308196
|
entity |
| Predicate | mediumForActivityInStory |
P107445
|
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: [River Floss, mediumForActivityInStory, boating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediumForActivityInStory Context triple: [River Floss, mediumForActivityInStory, boating]
-
A.
mediumCategory
Indicates the classification of an item or content according to the type or form of medium it belongs to (e.g., print, digital, audio, video).
-
B.
mediumAppearance
Indicates that an entity appears in or is featured within a particular medium (such as a work, format, or communication channel).
-
C.
medium
Indicates that an entity serves as the means, channel, or intermediary through which an action, communication, or effect is carried out between other entities.
-
D.
mediumDisplayed
Indicates that a particular medium (such as an image, video, or document) is being shown or rendered in a given context or interface.
-
E.
mediumIncludes
Indicates that a given medium contains, encompasses, or incorporates another item, component, or element within it.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97c7f91d08190aac2f6419d3ba992 |
completed | April 10, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69d96fa55b888190ab1612e93c41aec4 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d97c7d0598819080cab0a2314bc106 |
completed | April 10, 2026, 10:41 p.m. |
Created at: April 9, 2026, 5:39 p.m.