Triple

T37463563
Position Surface form Disambiguated ID Type / Status
Subject Rin, the First Disciple E930978 entity
Predicate relatedCard P37 FINISHED
Object The Fourth Seal
The Fourth Seal is a card from the Legends of Runeterra universe associated with Rin, the First Disciple, thematically tied to mystical or prophetic sealing powers.
E2232045 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: The Fourth Seal | Statement: [Rin, the First Disciple, relatedCard, The Fourth Seal]
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: The Fourth Seal
Triple: [Rin, the First Disciple, relatedCard, The Fourth Seal]
Generated description
The Fourth Seal is a card from the Legends of Runeterra universe associated with Rin, the First Disciple, thematically tied to mystical or prophetic sealing powers.

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_69f76ec1a1148190b0a961f188d621b0 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_6a03809e663c819080cff52d0377d81f completed May 12, 2026, 7:33 p.m.
NED1 Entity disambiguation (via context triple) batch_6a409ef570d08190a937a23dab2b04b1 completed June 28, 2026, 4:11 a.m.
NEDg Description generation batch_6a409ffd39648190b86e65c728810f62 completed June 28, 2026, 4:15 a.m.
NED2 Entity disambiguation (via description) batch_6a40a0c329908190acbd2d3cc33d29fc completed June 28, 2026, 4:19 a.m.
Created at: May 3, 2026, 4:17 p.m.