Triple
T38195651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiel Yacht Club |
E1005601
|
entity |
| Predicate | hasApproximateScope |
P397
|
FINISHED |
| Object | international |
—
|
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: international | Statement: [Kiel Yacht Club, hasApproximateScope, international]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateScope Context triple: [Kiel Yacht Club, hasApproximateScope, international]
-
A.
hasScope
chosen
Indicates that one entity defines, limits, or encompasses the range, extent, or applicability within which another entity operates or is valid.
-
B.
hasApproximateExtent
Indicates that one entity has a spatial, temporal, or quantitative extent that is only roughly or approximately specified rather than exact.
-
C.
hasApproximateUse
Indicates that one entity is used for a purpose that is similar to, but not exactly the same as, the use or function of another entity.
-
D.
hasRepresentationScope
Indicates that something is represented, described, or modeled only within a specified scope, context, or domain.
-
E.
hasRuleScope
Indicates that a rule is applicable within, or constrained to, a specific scope or context.
- 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_69f76dbd22f48190940318cea061e8bb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: May 3, 2026, 4:29 p.m.