Triple
T30208254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Lady ghost |
E767996
|
entity |
| Predicate | timePeriodOfLegends |
P25762
|
FINISHED |
| Object | post-medieval era |
—
|
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: post-medieval era | Statement: [Green Lady ghost, timePeriodOfLegends, post-medieval era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfLegends Context triple: [Green Lady ghost, timePeriodOfLegends, post-medieval era]
-
A.
legendaryPeriod
Indicates a time span associated with legends or mythic events rather than strictly historical chronology.
-
B.
timePeriodOfLegend
chosen
Indicates the time period during which a particular legend is traditionally set or believed to have occurred.
-
C.
timeInMyth
Indicates that an entity exists or occurs during a specific time period within a mythological narrative or tradition.
-
D.
dateInLegendarium
Indicates that a given date occurs within the fictional historical timeline (legendarium) of a particular narrative world.
-
E.
chronologyWithinMythos
Indicates that one event, story, or element occurs at a specific position or order within the internal timeline of a particular mythos or fictional universe.
- 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_69f2247eb0848190b4032f302d39c0d9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 29, 2026, 7:32 p.m.