Triple

T36833944
Position Surface form Disambiguated ID Type / Status
Subject Alcácer Quibir E910218 entity
Predicate historicalName P65 FINISHED
Object al-Qasr al-Kabir
Al-Qasr al-Kabir is a historic city in northern Morocco, best known as the site of the 1578 Battle of Alcácer Quibir that reshaped Portuguese and Moroccan history.
E2201209 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: al-Qasr al-Kabir | Statement: [Alcácer Quibir, historicalName, al-Qasr al-Kabir]
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: al-Qasr al-Kabir
Triple: [Alcácer Quibir, historicalName, al-Qasr al-Kabir]
Generated description
Al-Qasr al-Kabir is a historic city in northern Morocco, best known as the site of the 1578 Battle of Alcácer Quibir that reshaped Portuguese and Moroccan history.

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_69f76e7e9d60819092442fba73290a46 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f7cf7c7eb481908f66f6e614ae4d35 completed May 3, 2026, 10:43 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3dde6f78408190bafedbf04dcc84da completed June 26, 2026, 2:05 a.m.
NEDg Description generation batch_6a3de4b824e88190a8e246133862a9b7 completed June 26, 2026, 2:32 a.m.
NED2 Entity disambiguation (via description) batch_6a3df00752ec8190a8f9448e334b5e28 completed June 26, 2026, 3:20 a.m.
Created at: May 3, 2026, 4:13 p.m.