Triple
T9410281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wind of the Sea |
E226686
|
entity |
| Predicate | firstPowerDate |
P89015
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [Wind of the Sea, firstPowerDate, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPowerDate Context triple: [Wind of the Sea, firstPowerDate, 2013]
-
A.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
-
B.
firstReachedDate
Indicates the date on which a particular entity first achieved, accessed, or arrived at a specified state, location, or milestone.
-
C.
firstInternationalDate
Indicates that one entity is the earliest (chronologically first) international date associated with another entity.
-
D.
firstUsedOn
Indicates the date, time, or context in which something was initially applied, activated, or put into use on a particular object or entity.
-
E.
firstHolderDate
Indicates the date on which an entity first became the holder or owner of another entity (e.g., an asset, title, or right).
- F. None of above. chosen
Provenance (4 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_69ca843280488190bc65600e843ef9e6 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5255e4fc81908bf2f69c9a12ef83 |
completed | April 1, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca9d07eb08190866eb15333386dfa |
completed | April 1, 2026, 5:14 a.m. |
Created at: March 30, 2026, 7:47 p.m.