Triple
T29848525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longobards in Italy, Places of the Power (568–774 A.D.) |
E757999
|
entity |
| Predicate | startTimeRepresented |
P197413
|
FINISHED |
| Object | 568 |
—
|
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: 568 | Statement: [Longobards in Italy, Places of the Power (568–774 A.D.), startTimeRepresented, 568]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeRepresented Context triple: [Longobards in Italy, Places of the Power (568–774 A.D.), startTimeRepresented, 568]
-
A.
endTimeRepresented
Indicates that a specified time value denotes the point at which an event, state, or representation concludes.
-
B.
startTimeAsRepresentative
Indicates the time at which an entity begins serving or acting in a representative capacity.
-
C.
startTimeDepicted
Indicates that the subject visually represents the starting time of an event, process, or state.
-
D.
startTimeAsCardinal
Indicates the specific clock time at which an event or action begins, expressed as a cardinal (numeric) value rather than a textual or formatted time.
-
E.
positionStartTime
Indicates the time at which a position, role, or placement begins.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fe91383a1c81909266e40c3c3ede6c |
completed | May 9, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69fe8fde094081908f0f121664fbb5c7 |
completed | May 9, 2026, 1:37 a.m. |
| PDg | Predicate description generation | batch_69fe9137730c81909d1d57c30566c89a |
completed | May 9, 2026, 1:43 a.m. |
Created at: April 29, 2026, 5:43 p.m.