Triple
T16644113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Saxe-Eisenach |
E404419
|
entity |
| Predicate | firstCreationStart |
P14243
|
FINISHED |
| Object | 1596 |
—
|
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: 1596 | Statement: [House of Saxe-Eisenach, firstCreationStart, 1596]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCreationStart Context triple: [House of Saxe-Eisenach, firstCreationStart, 1596]
-
A.
firstCreationEndDate
Indicates the date on which the initial creation or establishment of something was completed or came to an end.
-
B.
firstCreatedAt
chosen
Indicates the time or date at which an entity was initially created for the first time.
-
C.
firstCreatedUsing
Indicates that one entity was initially produced or brought into existence through the use, application, or involvement of another entity.
-
D.
firstCreationYear
Indicates the year in which something was first created or originally produced.
-
E.
firstRunAt
Indicates the date and time at which an entity was first executed, launched, or run.
- 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.