Triple
T11046934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beren and Lúthien |
E261158
|
entity |
| Predicate | timePeriodInLegendarium |
P25762
|
FINISHED |
| Object | First Age of Middle-earth |
—
|
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: First Age of Middle-earth | Statement: [Beren and Lúthien, timePeriodInLegendarium, First Age of Middle-earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodInLegendarium Context triple: [Beren and Lúthien, timePeriodInLegendarium, First Age of Middle-earth]
-
A.
timeInMyth
Indicates that an entity exists or occurs during a specific time period within a mythological narrative or tradition.
-
B.
timePeriodOfLegend
chosen
Indicates the time period during which a particular legend is traditionally set or believed to have occurred.
-
C.
timePeriodOfDominance
Indicates the span of time during which an entity held dominance, control, or prevailing influence over another entity or context.
-
D.
timeExistence
Indicates the period or duration during which an entity exists or is valid.
-
E.
timePeriodOftenDepicted
Indicates that one entity is a time period that is frequently represented or portrayed in depictions involving the other 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798307da481908996557a73c9b49a |
completed | April 9, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.