Triple
T23432750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glen Affric |
E563375
|
entity |
| Predicate | containsMountain |
P10602
|
FINISHED |
| Object |
Sgùrr na Lapaich
Sgùrr na Lapaich is a prominent Scottish mountain in the Northwest Highlands, noted for its rugged terrain and expansive views over Glen Affric.
|
E1600935
|
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: Sgùrr na Lapaich | Statement: [Glen Affric, containsMountain, Sgùrr na Lapaich]
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: Sgùrr na Lapaich Triple: [Glen Affric, containsMountain, Sgùrr na Lapaich]
Generated description
Sgùrr na Lapaich is a prominent Scottish mountain in the Northwest Highlands, noted for its rugged terrain and expansive views over Glen Affric.
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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5d920548190904f80c7c40cba06 |
completed | April 29, 2026, 6:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0f53771ff48190bb0f2ad5ebf2587b |
completed | May 21, 2026, 6:48 p.m. |
| NEDg | Description generation | batch_6a0f54d5f37481909f3bf36772aa3493 |
completed | May 21, 2026, 6:54 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0f55a3a5588190bd6313aacab674a4 |
completed | May 21, 2026, 6:57 p.m. |
Created at: April 17, 2026, 5:49 p.m.