Triple
T2133166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glamorous Glennis |
E46588
|
entity |
| Predicate | notableDateAssociation |
P925
|
FINISHED |
| Object | 14 October 1947 |
—
|
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: 14 October 1947 | Statement: [Glamorous Glennis, notableDateAssociation, 14 October 1947]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDateAssociation Context triple: [Glamorous Glennis, notableDateAssociation, 14 October 1947]
-
A.
notableEventDate
chosen
Indicates the date on which a notable or significant event associated with the subject occurred.
-
B.
periodCommemorated
Indicates that something serves to honor, remember, or mark a specific historical or temporal period.
-
C.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
D.
notableEventResponse
Indicates a response, reaction, or consequence that occurs as a result of a notable event.
-
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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbba0c42c8190ab3ce4bbf1531ee1 |
completed | March 7, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69abb7bf56e481909b0f497d238451cc |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.