Triple
T444409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethics (Spinoza) |
E10185
|
entity |
| Predicate | dateOfFirstPublication |
P25
|
FINISHED |
| Object | 1677 |
—
|
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: 1677 | Statement: [Ethics (Spinoza), dateOfFirstPublication, 1677]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfFirstPublication Context triple: [Ethics (Spinoza), dateOfFirstPublication, 1677]
-
A.
publicationYear
chosen
Indicates the specific calendar year in which a work was formally published or released.
-
B.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
-
C.
firstPublisher
Indicates that an entity is the original or earliest publisher of another entity (such as a work, edition, or resource).
-
D.
publicationPeriod
Indicates the span of time during which something is published, active in publication, or valid as a published work.
-
E.
firstAppeared
Indicates the earliest known time or context in which an entity was introduced, observed, or came into existence.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef459800819083cd9eef3e7b5295 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2edde2b9c8190bd20b582eb4c5065 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.