Triple
T9141178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Botany Bay |
E219329
|
entity |
| Predicate | firstEuropeanLandingBy |
P77677
|
FINISHED |
| Object | crew of HMS Endeavour |
—
|
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: crew of HMS Endeavour | Statement: [Botany Bay, firstEuropeanLandingBy, crew of HMS Endeavour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEuropeanLandingBy Context triple: [Botany Bay, firstEuropeanLandingBy, crew of HMS Endeavour]
-
A.
firstEuropeanClaimBy
Indicates that a place or territory was first formally claimed or asserted as possession by a specified European individual, group, or state.
-
B.
firstEuropeanLandingInIndiaBy
Indicates the person or group credited with making the earliest recorded European landing in India.
-
C.
firstLandingBy
chosen
Indicates that one entity is the earliest or initial instance to arrive, land, or touch down at a particular place or target relative to others.
-
D.
firstChartedOn
Indicates that an entity was first mapped, recorded, or charted on a specific date or during a specific time.
-
E.
yearOfEuropeanExploration
Indicates the specific year in which a European exploration of the referenced entity 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_69ca83e012288190a5771058adbaabd2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8f4df5c8190808edfa7c453a51c |
completed | April 1, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69cc6603ce8c8190bf6e8d6754bdec54 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:19 p.m.