Triple
T23203034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faroese rowing |
E580369
|
entity |
| Predicate | boatFeature |
P81629
|
FINISHED |
| Object | narrow and long hulls |
—
|
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: narrow and long hulls | Statement: [Faroese rowing, boatFeature, narrow and long hulls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boatFeature Context triple: [Faroese rowing, boatFeature, narrow and long hulls]
-
A.
marineAttraction
Indicates a relationship where one entity serves as a point of interest or entertainment specifically related to marine life or the marine environment for another entity.
-
B.
boatConfiguration
chosen
Indicates the specific arrangement, layout, or setup of components or features on a boat.
-
C.
isBoatingLandmark
Indicates that a location serves as a notable reference point or feature specifically used for boating navigation or activities.
-
D.
shipFeatured
Indicates that a particular ship is highlighted or promoted as a featured item in a given context.
-
E.
hasBoatFacility
Indicates that an entity provides or is equipped with facilities or services specifically for boats.
- 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.