Triple
T5840425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tune ship |
E129578
|
entity |
| Predicate | excavatedInYear |
P31970
|
FINISHED |
| Object | 1867 |
—
|
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: 1867 | Statement: [Tune ship, excavatedInYear, 1867]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excavatedInYear Context triple: [Tune ship, excavatedInYear, 1867]
-
A.
excavationYear
chosen
Indicates the year in which an excavation activity took place or was conducted.
-
B.
excavatedAt
Indicates that an excavation activity took place at a specific location or site.
-
C.
excavatedIn
Indicates that something (typically an artifact, structure, or site) was uncovered or dug out during an excavation that took place at a specific time or within a specific time period.
-
D.
excavatedFrom
Indicates that something (typically an artifact, fossil, or material) was dug out or uncovered from a specific location or source through excavation.
-
E.
excavatedBy
Indicates that something (typically an archaeological site, artifact, or geological feature) was uncovered or dug out by a particular agent (such as a person, team, or organization).
- 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_69c0084bd31c8190a796bb6284845e83 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c0334412388190bc594794ec5754f9 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:54 p.m.