Triple
T23203043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faroese rowing |
E580369
|
entity |
| Predicate | hasRelatedActivity |
P48591
|
FINISHED |
| Object | Faroese boatbuilding |
—
|
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: Faroese boatbuilding | Statement: [Faroese rowing, hasRelatedActivity, Faroese boatbuilding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelatedActivity Context triple: [Faroese rowing, hasRelatedActivity, Faroese boatbuilding]
-
A.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
B.
associatedActivity
chosen
Indicates that one entity is linked to, involved in, or characterized by a particular activity or set of activities.
-
C.
hasBasedActivity
Indicates that one activity is founded on, derived from, or primarily driven by another underlying activity.
-
D.
hasSubjectActivity
Indicates that an entity is associated with or participates in a particular activity as its subject.
-
E.
hasChildrenActivities
Indicates that an entity is associated with one or more activities specifically intended for children.
- 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_69e24602ae1481908aaa6bc7ca493867 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1907a8bb48190846802a24d33bccf |
completed | April 29, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:07 p.m.