Triple
T1388864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape of Good Hope |
E29908
|
entity |
| Predicate | firstEuropeanSightingYear |
P413
|
FINISHED |
| Object | 1488 |
—
|
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: 1488 | Statement: [Cape of Good Hope, firstEuropeanSightingYear, 1488]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEuropeanSightingYear Context triple: [Cape of Good Hope, firstEuropeanSightingYear, 1488]
-
A.
firstReportedYear
Indicates the year in which something was initially reported, documented, or made known for the first time.
-
B.
firstCelebratedInYear
Indicates the year in which something (such as an event, holiday, or celebration) was first observed or celebrated.
-
C.
discoveryDate
Indicates the date on which something was first discovered or identified.
-
D.
yearOfEuropeanExploration
chosen
Indicates the specific year in which a European exploration of the referenced entity took place.
-
E.
firstVoyageEndYear
Indicates the calendar year in which an entity’s first voyage or initial journey was completed or came to an end.
- 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c35ce48c81909aaad7dfa2df63fa |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4beffcf808190ab4cd0271257ce63 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.