Triple
T15618382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bursledon |
E375477
|
entity |
| Predicate | modernActivity |
P61745
|
FINISHED |
| Object | yachting and leisure 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: yachting and leisure boating | Statement: [Bursledon, modernActivity, yachting and leisure boating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernActivity Context triple: [Bursledon, modernActivity, yachting and leisure boating]
-
A.
modernActivities
chosen
Indicates that the associated activities are contemporary or characteristic of the modern era, as opposed to traditional or historical practices.
-
B.
hasContemporaryActivity
Indicates that two activities occur during the same time period or overlap in time.
-
C.
earnActivity
Indicates that an entity gains or receives something of value (such as money, points, or rewards) as a result of performing a particular activity.
-
D.
activityTime
Indicates the time period during which an activity occurs or is scheduled to take place.
-
E.
communityActivity
Indicates that an entity participates in, contributes to, or is involved with activities organized for or by a community.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e997ce481909b2f10d25705fbc6 |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:13 a.m.