Triple
T37889498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocky Point |
E945086
|
entity |
| Predicate | boardTypeRecommended |
P71981
|
FINISHED |
| Object | high-performance shortboard |
—
|
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: high-performance shortboard | Statement: [Rocky Point, boardTypeRecommended, high-performance shortboard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boardTypeRecommended Context triple: [Rocky Point, boardTypeRecommended, high-performance shortboard]
-
A.
boardIncluded
Indicates that a particular board is part of, or contained within, a larger set, system, or structure.
-
B.
hasBoardType
chosen
Indicates that an entity is associated with or uses a specific type or category of board.
-
C.
boardName
Indicates the name or title assigned to a specific board within a system or context.
-
D.
boardPlan
Indicates that an agent gets onto or enters a planned vehicle, vessel, or mode of transport as part of a scheduled journey.
-
E.
boardProperties
Indicates a relationship where specific attributes or characteristics are assigned to or associated with a board.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:19 p.m.