Triple
T31292458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marilyns of Wales |
E797975
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object |
Anglesey Marilyns
Anglesey Marilyns are the hills on the island of Anglesey in Wales that qualify as Marilyns, each having a prominence of at least 150 meters.
|
E1955073
|
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: Anglesey Marilyns | Statement: [Marilyns of Wales, hasPart, Anglesey Marilyns]
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: Anglesey Marilyns Triple: [Marilyns of Wales, hasPart, Anglesey Marilyns]
Generated description
Anglesey Marilyns are the hills on the island of Anglesey in Wales that qualify as Marilyns, each having a prominence of at least 150 meters.
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_69f224dfde288190af313f3c221c857e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69e2e24c48190b3342bf23c491d9b |
completed | May 3, 2026, 1 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2a1e336fd08190a9cf0515a7674e2c |
completed | June 11, 2026, 2:32 a.m. |
| NEDg | Description generation | batch_6a2a284d81fc819097af9a3b70f9f356 |
completed | June 11, 2026, 3:15 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a2a28ce1320819097156336ff1bfefd |
completed | June 11, 2026, 3:17 a.m. |
Created at: April 29, 2026, 9:14 p.m.