Triple
T37262253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batavia shipwreck |
E924285
|
entity |
| Predicate | periodOfMajorExcavation |
P7651
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Batavia shipwreck, periodOfMajorExcavation, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodOfMajorExcavation Context triple: [Batavia shipwreck, periodOfMajorExcavation, 1970s]
-
A.
timeSpanOfExcavations
Indicates the duration or period of time during which the excavations took place.
-
B.
excavationYear
Indicates the year in which an excavation activity took place or was conducted.
-
C.
periodOfMajorRemains
Indicates the historical time period during which the primary surviving remains or artifacts associated with something were created or are dated.
-
D.
firstExcavationYear
Indicates the calendar year in which an excavation activity at a given site or object was first carried out.
-
E.
majorExcavationsBegan
chosen
Indicates that significant archaeological or construction excavation work was initiated at a particular time or for a particular project.
- 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 3, 2026, 4:15 p.m.