Triple
T19016961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterford Tugboat Roundup |
E465375
|
entity |
| Predicate | transportModeHighlighted |
P86086
|
FINISHED |
| Object | tugboat |
—
|
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: tugboat | Statement: [Waterford Tugboat Roundup, transportModeHighlighted, tugboat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportModeHighlighted Context triple: [Waterford Tugboat Roundup, transportModeHighlighted, tugboat]
-
A.
transportModeImportant
Indicates that the mode of transport used is considered significant or plays an important role in the context of the relationship or action.
-
B.
transportModePresent
chosen
Indicates that a particular mode of transportation is involved or available in the described context or event.
-
C.
transportModeTo
Indicates the means or mode of transportation used to travel to a specified destination.
-
D.
transportPattern
Indicates a recurring or characteristic way in which transportation is carried out between entities, such as typical routes, modes, or schedules.
-
E.
transportTheme
Indicates that an agent or instrument moves or carries a theme (entity) from one place or state to another.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6dc0f9081909cddc5186603e885 |
completed | April 20, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.