Triple
T385317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fannette Island |
E8767
|
entity |
| Predicate | teahouseBuiltFor |
P9494
|
FINISHED |
| Object | Vikingsholm owner |
—
|
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: Vikingsholm owner | Statement: [Fannette Island, teahouseBuiltFor, Vikingsholm owner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teahouseBuiltFor Context triple: [Fannette Island, teahouseBuiltFor, Vikingsholm owner]
-
A.
estimatedTeaWeight
Indicates the quantified amount of tea that is approximated or predicted in weight rather than precisely measured.
-
B.
hasTeeType
Indicates that an entity (typically a golf hole or course) is associated with a specific type or category of tee.
-
C.
domesticCup
Indicates that an entity has won or participated in a domestic (national-level) cup competition within its sport or domain.
-
D.
housesCollection
Indicates that one entity serves as a container or repository that holds or stores a collection of other entities.
-
E.
isDesignedFor
chosen
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec4345a48190a413261cba4eafd7 |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e967d84c8190a6b647f78d95d4e4 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.