Triple
T3545880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samuel Hearne |
E74994
|
entity |
| Predicate | notableWorkPublicationYear |
P38930
|
FINISHED |
| Object | 1795 |
—
|
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: 1795 | Statement: [Samuel Hearne, notableWorkPublicationYear, 1795]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWorkPublicationYear Context triple: [Samuel Hearne, notableWorkPublicationYear, 1795]
-
A.
notableWorkPublicationDate
chosen
Indicates the date on which a notable work associated with an entity was first published.
-
B.
notableWorkAuthor
Indicates that one entity is the creator or author of a notable work associated with another entity.
-
C.
notableWorkIn
Indicates that an entity is known for or associated with a significant work, contribution, or achievement in a particular field or context.
-
D.
notableWorkYear
Indicates the year in which a notable work associated with an entity was created, released, or achieved prominence.
-
E.
notableWorkWith
Indicates a relationship where two or more entities are recognized for having collaborated on or been jointly associated with a significant work or 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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbf77d938819095c72a88b5af644a |
completed | March 8, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_69adae15749881909b847c6ca73c934e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:20 p.m.