Triple
T25711807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clara Eißner |
E644751
|
entity |
| Predicate | proposedAtDate |
P123043
|
FINISHED |
| Object | 1910-08 |
—
|
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: 1910-08 | Statement: [Clara Eißner, proposedAtDate, 1910-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedAtDate Context triple: [Clara Eißner, proposedAtDate, 1910-08]
-
A.
proposalDate
Indicates the date on which a proposal is formally made or submitted from one entity to another.
-
B.
proposedInMonth
chosen
Indicates that an entity (such as a proposal or plan) was formally proposed during a specific calendar month.
-
C.
proposedInYear
Indicates that something, such as a plan, idea, or piece of legislation, was formally put forward or suggested in a specific calendar year.
-
D.
hasAlternativeProposedDate
Indicates that an alternative date has been suggested or proposed in place of an original scheduled date.
-
E.
plannedAt
Indicates that an event, action, or activity is scheduled or intended to occur at a specific time or date.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 21, 2026, 9:16 p.m.