Triple

T26087202
Position Surface form Disambiguated ID Type / Status
Subject Sacra Liga E658015 entity
Predicate hasAlternativeName P39 FINISHED
Object Sacred League
The Sacred League was a coalition of Greek city-states formed in antiquity to protect and administer important religious sanctuaries and uphold shared sacred obligations.
E1708328 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: Sacred League | Statement: [Sacra Liga, hasAlternativeName, Sacred League]
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: Sacred League
Triple: [Sacra Liga, hasAlternativeName, Sacred League]
Generated description
The Sacred League was a coalition of Greek city-states formed in antiquity to protect and administer important religious sanctuaries and uphold shared sacred obligations.

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_69ee5bbfc4d08190a1b206d0ac3a1e8d completed April 26, 2026, 6:38 p.m.
NER Named-entity recognition batch_69f60700de00819098c562334e53ad87 completed May 2, 2026, 2:15 p.m.
NED1 Entity disambiguation (via context triple) batch_6a111b39dc60819091f0625129f0e718 completed May 23, 2026, 3:12 a.m.
NEDg Description generation batch_6a111c0a65f881908a29d01412627de9 completed May 23, 2026, 3:16 a.m.
NED2 Entity disambiguation (via description) batch_6a111ca03b088190937f673d972fdca2 completed May 23, 2026, 3:18 a.m.
Created at: April 26, 2026, 7:44 p.m.