Triple
T26929270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cruising Yacht Club of Australia |
E678167
|
entity |
| Predicate | hasNotableEventStartYear |
P87721
|
FINISHED |
| Object | 1945 |
—
|
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: 1945 | Statement: [Cruising Yacht Club of Australia, hasNotableEventStartYear, 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableEventStartYear Context triple: [Cruising Yacht Club of Australia, hasNotableEventStartYear, 1945]
-
A.
hasHistoricEventYear
Indicates the specific year in which a referenced historic event took place.
-
B.
hasNotableYear
chosen
Indicates that an entity is associated with a specific year that is particularly significant or noteworthy for it.
-
C.
beganInYear
Indicates that an event, process, or state started in a specific calendar year.
-
D.
notableWorkPeriodStart
Indicates the point in time when an entity’s period of producing its notable work or works begins.
-
E.
hasYearOfNamesakeEvent
Indicates the specific year in which the event that a namesake is based on or named after took place.
- 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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: April 27, 2026, 6:11 a.m.