Triple
T29726578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theodebald |
E752194
|
entity |
| Predicate | hasUsageRegionHistorical |
P64171
|
FINISHED |
| Object | Frankish realms |
—
|
NE NERFINISHED |
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: Frankish realms | Statement: [Theodebald, hasUsageRegionHistorical, Frankish realms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUsageRegionHistorical Context triple: [Theodebald, hasUsageRegionHistorical, Frankish realms]
-
A.
hasHistoricalUsageIn
chosen
Indicates that something has been used or practiced within a particular historical period, context, or tradition.
-
B.
hasHistoricalRegionType
Indicates that a historical region is associated with a specific type or classification of historical region.
-
C.
hasHomeRegionHistorical
Indicates that an entity is historically associated with or originates from a particular home region.
-
D.
isHistoricRegionFor
Indicates that one entity serves as a historically recognized region associated with, or significant to, another entity.
-
E.
historicallyIncludedRegion
Indicates that one region was formerly part of, or contained within, another region during a past historical 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 7:39 p.m.