Triple
T1300680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gay Head |
E27755
|
entity |
| Predicate | hasTraditionalActivities |
P19423
|
FINISHED |
| Object | fishing |
—
|
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: fishing | Statement: [Gay Head, hasTraditionalActivities, fishing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalActivities Context triple: [Gay Head, hasTraditionalActivities, fishing]
-
A.
hasTraditionIn
chosen
Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
-
B.
hasRecreationActivity
Indicates that an entity provides, includes, or is associated with a particular recreational activity.
-
C.
hasTraditionalDance
Indicates that an entity is associated with, practices, or possesses a specific traditional dance.
-
D.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
E.
hasCulturalEvent
Indicates that a cultural event (such as a festival, performance, or exhibition) takes place in, is associated with, or is hosted by a given entity.
- 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_69a496d6682881909ba658f1c1e0e2b0 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c1145c2481908adf22dfd6ce349b |
completed | March 1, 2026, 10:43 p.m. |
| PD | Predicate disambiguation | batch_69a4bee8544c8190874efd9bae9bccf9 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.