Triple
T31808332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danewerk |
E811934
|
entity |
| Predicate | earliestSectionsDateTo |
P181080
|
FINISHED |
| Object | early Middle Ages |
—
|
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: early Middle Ages | Statement: [Danewerk, earliestSectionsDateTo, early Middle Ages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestSectionsDateTo Context triple: [Danewerk, earliestSectionsDateTo, early Middle Ages]
-
A.
earliestDate
Indicates the earliest point in time at which an associated event, state, or relationship is considered to begin or be valid.
-
B.
earliestVersionDate
Indicates the date on which the earliest known or first version of an entity was created, released, or became valid.
-
C.
earliestDocumentsDate
Indicates the earliest date on which the associated documents were created, recorded, or became valid.
-
D.
latestEntriesDateFrom
Indicates the starting date from which the most recent entries in a set or system are considered or retrieved.
-
E.
earliestStrataDate
Indicates the earliest known or recorded date associated with a particular geological or archaeological stratum.
- F. None of above. chosen
Provenance (4 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
| PDg | Predicate description generation | batch_69f760a2a90c8190b8fbc55412ab752b |
completed | May 3, 2026, 2:50 p.m. |
Created at: April 30, 2026, 11:43 p.m.