Triple
T16644118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Saxe-Eisenach |
E404419
|
entity |
| Predicate | thirdCreationEnd |
P87824
|
FINISHED |
| Object | 1741 |
—
|
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: 1741 | Statement: [House of Saxe-Eisenach, thirdCreationEnd, 1741]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdCreationEnd Context triple: [House of Saxe-Eisenach, thirdCreationEnd, 1741]
-
A.
thirdCreationStatus
Indicates the status or outcome of a third instance or attempt of a creation process in relation to an entity.
-
B.
thirdGenerationEnd
Indicates that a third generation in a sequence, lineage, or process has reached its endpoint or conclusion.
-
C.
thirdCreationYear
chosen
Indicates the year in which an entity’s third instance, version, or creation in a sequence was produced or came into existence.
-
D.
thirdCreatedBy
Indicates that the third item in a sequence or set was created by a specified agent or creator.
-
E.
firstCreationEndDate
Indicates the date on which the initial creation or establishment of something was completed or came to an end.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ad3b12c8190a32e33d9ecff9dae |
completed | April 18, 2026, 12:36 p.m. |
| PD | Predicate disambiguation | batch_69e296af2f88819092c9ffee4a65d7dd |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:18 a.m.