Triple
T37581264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Double inconstance (stage role) |
E934967
|
entity |
| Predicate | hasSourceWorkPublicationCentury |
P1998
|
FINISHED |
| Object | 18th century |
—
|
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: 18th century | Statement: [La Double inconstance (stage role), hasSourceWorkPublicationCentury, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSourceWorkPublicationCentury Context triple: [La Double inconstance (stage role), hasSourceWorkPublicationCentury, 18th century]
-
A.
hasWorkPublicationCentury
Indicates the century during which a given work was published.
-
B.
firstWorkPublicationCentury
Indicates the century in which an entity’s first work was originally published.
-
C.
isSetInWorkPublishedInCentury
Indicates that the setting of a work takes place in another work that was published in a specified century.
-
D.
publicationCentury
chosen
Indicates the century during which a work was published.
-
E.
basedOnWorkPublicationDecade
Indicates that one entity is categorized or related to another based on the decade in which a referenced work was originally published.
- 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_69f76ece61dc8190a0ab33f8d87d0a7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: May 3, 2026, 4:17 p.m.