Triple
T13327038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terra Repromissionis |
E317466
|
entity |
| Predicate | timeOfLegend |
P20414
|
FINISHED |
| Object | early medieval period |
—
|
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 medieval period | Statement: [Terra Repromissionis, timeOfLegend, early medieval period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfLegend Context triple: [Terra Repromissionis, timeOfLegend, early medieval period]
-
A.
timeInMyth
chosen
Indicates that an entity exists or occurs during a specific time period within a mythological narrative or tradition.
-
B.
famousLegend
Indicates that the subject is widely known and celebrated in stories, myths, or folklore, often with enduring cultural significance.
-
C.
timeExistence
Indicates the period or duration during which an entity exists or is valid.
-
D.
timePeriodOfDominance
Indicates the span of time during which an entity held dominance, control, or prevailing influence over another entity or context.
-
E.
bestKnownLegend
Indicates that one entity is the most prominent or widely recognized legendary story or myth associated with another entity.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6babd88190a5d529df9584b9a4 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:30 p.m.