Triple
T4485496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canoes surf break |
E107227
|
entity |
| Predicate | boardRecommendation |
P16857
|
FINISHED |
| Object | longboard |
—
|
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: longboard | Statement: [Canoes surf break, boardRecommendation, longboard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boardRecommendation Context triple: [Canoes surf break, boardRecommendation, longboard]
-
A.
recommendedEquipment
chosen
Indicates that one entity suggests or endorses another entity as suitable equipment to be used in a particular context or activity.
-
B.
board
Indicates that an agent gets onto or into a vehicle, vessel, or craft in order to travel or be transported.
-
C.
bookSelection
Indicates the act or result of choosing a particular book from a set of available options.
-
D.
mainBoardName
Indicates the name or designation assigned to a main board (e.g., primary circuit board or central hardware board) associated with an entity.
-
E.
commendedFor
Indicates that one entity has expressed praise or approval toward another entity specifically because of a particular action, quality, or achievement.
- 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_69bd43f84f788190a1383579c4a595be |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd556d29f08190bab1e872dd7e819f |
completed | March 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69bd5213e3d0819094b026989e686f01 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 12:59 p.m.