Triple
T29587823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French Romantic theatre |
E754069
|
entity |
| Predicate | importantEventDate |
P925
|
FINISHED |
| Object | 1830 |
—
|
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: 1830 | Statement: [French Romantic theatre, importantEventDate, 1830]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importantEventDate Context triple: [French Romantic theatre, importantEventDate, 1830]
-
A.
dateEvent
Indicates that an event takes place or is scheduled on a specific date.
-
B.
capitalEventDate
Indicates the date on which a capital-related event (such as establishment, designation, or change of capital status) occurred.
-
C.
mainEventDate
Indicates the primary or most significant date on which the referenced event occurs or is scheduled to occur.
-
D.
notableEventDate
chosen
Indicates the date on which a notable or significant event associated with the subject occurred.
-
E.
dateSignificance
Indicates the specific importance, meaning, or notable role that a particular date holds within a given context or relationship.
- 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_69f0ef836ac88190bd809dc58b5ec907 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 28, 2026, 6:12 p.m.