Triple
T25528605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Îles Sanguinaires |
E639845
|
entity |
| Predicate | hasHighestPoint |
P210
|
FINISHED |
| Object |
Mezu Mare
Mezu Mare is the highest peak of the Îles Sanguinaires, a small archipelago off the west coast of Corsica in the Mediterranean Sea.
|
E1685065
|
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: Mezu Mare | Statement: [Îles Sanguinaires, hasHighestPoint, Mezu Mare]
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: Mezu Mare Triple: [Îles Sanguinaires, hasHighestPoint, Mezu Mare]
Generated description
Mezu Mare is the highest peak of the Îles Sanguinaires, a small archipelago off the west coast of Corsica in the Mediterranean Sea.
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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f861402081908ba57a30038c2fa2 |
completed | May 2, 2026, 1:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a10ad8ae6708190b86485b45508f57a |
completed | May 22, 2026, 7:24 p.m. |
| NEDg | Description generation | batch_6a10af85fbb88190bc339e559415d579 |
completed | May 22, 2026, 7:33 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a10aff5f7e081908fbf0815b69832b8 |
completed | May 22, 2026, 7:35 p.m. |
Created at: April 21, 2026, 3:12 p.m.