Triple
T27603485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Corinthian Yacht Club |
E700114
|
entity |
| Predicate | hasJuniorSailingProgram |
P6626
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Royal Corinthian Yacht Club, hasJuniorSailingProgram, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJuniorSailingProgram Context triple: [Royal Corinthian Yacht Club, hasJuniorSailingProgram, yes]
-
A.
juniorProgram
Indicates that one entity holds a junior or subordinate program position or role in relation to another entity.
-
B.
hasYouthProgram
chosen
Indicates that an entity offers or is associated with an organized program or set of activities specifically designed for young people.
-
C.
hasCadetProgram
Indicates that an organization or entity offers or operates a cadet program for training or development.
-
D.
hasJuniorAgeCategory
Indicates that an entity is associated with, or classified under, a junior age category within a given context or system.
-
E.
hasJuniorSection
Indicates that an entity includes or is associated with a subordinate or lower-level section within its structure or organization.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 2:09 p.m.