Triple
T4261755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gesta Francorum |
E96119
|
entity |
| Predicate | chronicleCoverageStart |
P9200
|
FINISHED |
| Object | 1095 |
—
|
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: 1095 | Statement: [Gesta Francorum, chronicleCoverageStart, 1095]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronicleCoverageStart Context triple: [Gesta Francorum, chronicleCoverageStart, 1095]
-
A.
chronologicallyCovers
Indicates that one time period, event, or sequence extends over and includes the entire chronological span of another.
-
B.
chronicledBy
Indicates that something is documented, recorded, or described in detail by a particular source, author, or record.
-
C.
mediaCoverageStartDate
Indicates the date on which media coverage of an entity, event, or subject begins.
-
D.
notableEventCoverage
Indicates that there is media or documented coverage specifically focused on a notable event related to the subject.
-
E.
coversPeriodStart
chosen
Indicates that the time span or coverage of one entity begins at, or includes, the specified starting point in time of another entity or period.
- 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_69b3454095ac81909c2494f7ff294af1 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34f82b2688190bf4c581e13a9c4b9 |
completed | March 12, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69b347f8dcb08190a725c1f7fb5a7466 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.