Triple
T12960038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Recherche de l’absolu |
E310115
|
entity |
| Predicate | hasApproximatePublicationPeriod |
P3627
|
FINISHED |
| Object | 1830s |
—
|
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: 1830s | Statement: [La Recherche de l’absolu, hasApproximatePublicationPeriod, 1830s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximatePublicationPeriod Context triple: [La Recherche de l’absolu, hasApproximatePublicationPeriod, 1830s]
-
A.
hasApproximatePublicationStart
Indicates that an entity is associated with an estimated or imprecise starting date for its publication.
-
B.
hasPublicationDate
Indicates that an entity is associated with the specific date on which it was published.
-
C.
publicationPeriod
chosen
Indicates the span of time during which something is published, active in publication, or valid as a published work.
-
D.
isPublishedWith
Indicates that an entity is released or made publicly available together with another specified entity, typically as part of the same publication or release event.
-
E.
firstPublicationPeriod
Indicates the time span during which something was first published or initially made publicly available.
- 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97dba57988190b786ffed55687a72 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:44 p.m.