Triple
T28303309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abel of Denmark |
E713764
|
entity |
| Predicate | titleStart-DukeOfSchleswig |
P112680
|
FINISHED |
| Object | 1232 |
—
|
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: 1232 | Statement: [Abel of Denmark, titleStart-DukeOfSchleswig, 1232]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleStart-DukeOfSchleswig Context triple: [Abel of Denmark, titleStart-DukeOfSchleswig, 1232]
-
A.
startTime (Duke of Bavaria)
Indicates the point in time at which the person began holding the title or office of Duke of Bavaria.
-
B.
recognizedAsDuke
Indicates that an entity is formally acknowledged or accepted as holding the title or status of a duke.
-
C.
lastSovereignDuke
Indicates that the subject is the final individual to hold the title of sovereign duke over a given territory or domain.
-
D.
startTime (Duke of Saxony)
Indicates the point in time at which the individual became the Duke of Saxony.
-
E.
reignAsDukeFrom
chosen
Indicates that an entity holds and exercises the title and authority of duke over a domain starting from a specified time.
- 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_69efb524ab688190a1ce7ee7c9520932 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: April 27, 2026, 11:36 p.m.