Triple

T25508484
Position Surface form Disambiguated ID Type / Status
Subject Faerie Land E639307 entity
Predicate hasNotableLocation P3858 FINISHED
Object Lucifera’s court
Lucifera’s court is the decadent and allegorical royal court ruled by the proud queen Lucifera in Edmund Spenser’s epic poem *The Faerie Queene*.
E1684046 NE 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: Lucifera’s court | Statement: [Faerie Land, hasNotableLocation, Lucifera’s court]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Lucifera’s court
Triple: [Faerie Land, hasNotableLocation, Lucifera’s court]
Generated description
Lucifera’s court is the decadent and allegorical royal court ruled by the proud queen Lucifera in Edmund Spenser’s epic poem *The Faerie Queene*.

Provenance (5 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_69e75dbd09308190b6b5f0afdc12ec6d completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f80844488190bbbaa6bd2e487940 completed May 2, 2026, 1:11 p.m.
NED1 Entity disambiguation (via context triple) batch_6a10ad7d5c1081908f7658de29362c5b completed May 22, 2026, 7:24 p.m.
NEDg Description generation batch_6a10ae7ea0088190bdefa7c31fe2859d completed May 22, 2026, 7:29 p.m.
NED2 Entity disambiguation (via description) batch_6a10af62078481908759f9df2167d81f completed May 22, 2026, 7:32 p.m.
Created at: April 21, 2026, 2:48 p.m.