Triple
T9776831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milford Sound |
E237267
|
entity |
| Predicate | EuropeanDiscoveryCentury |
P47542
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Milford Sound, EuropeanDiscoveryCentury, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EuropeanDiscoveryCentury Context triple: [Milford Sound, EuropeanDiscoveryCentury, 19th century]
-
A.
yearOfEuropeanExploration
Indicates the specific year in which a European exploration of the referenced entity took place.
-
B.
regionBefore1492
Indicates that one region existed or was defined prior to the year 1492 in relation to another region or temporal reference.
-
C.
firstChartedOn
chosen
Indicates that an entity was first mapped, recorded, or charted on a specific date or during a specific time.
-
D.
earliestEuropeanSettlementCentury
Indicates the century during which the earliest European settlement associated with the subject was established.
-
E.
firstEuropeanLandingDate
Indicates the date on which Europeans first arrived at or made landfall in a particular 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_69ca84d975a08190aab25b02a89bdab3 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda133ef548190aaecdf49de9c5aa8 |
completed | April 1, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:26 p.m.