Triple
T3438867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norse voyages to North America |
E72520
|
entity |
| Predicate | latestApproximateDate |
P877
|
FINISHED |
| Object | c. 1020 |
—
|
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: c. 1020 | Statement: [Norse voyages to North America, latestApproximateDate, c. 1020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: latestApproximateDate Context triple: [Norse voyages to North America, latestApproximateDate, c. 1020]
-
A.
latestPossibleDate
Indicates the most recent date on which a given event, condition, or state can validly or feasibly occur.
-
B.
dateApproximate
chosen
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
C.
latestReleaseDate
Indicates the date on which the most recent version or release of an entity became available.
-
D.
latestTime
Indicates the most recent point in time at which the related event, state, or condition occurs or is valid among a set of possible times.
-
E.
lastEntryDate
Indicates the date on which the most recent entry, record, or update associated with the subject occurred.
- 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_69ad85af50288190a854b76653deee6f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9f6de1481909b789f4b0e1113d3 |
completed | March 8, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69adae00ad588190bef24373b58a2e1a |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.