Triple
T25086347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Almus (son of Sisyphus) |
E628332
|
entity |
| Predicate | associatedToponym |
P122228
|
FINISHED |
| Object | Almones |
—
|
NE NERFINISHED |
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: Almones | Statement: [Almus (son of Sisyphus), associatedToponym, Almones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedToponym Context triple: [Almus (son of Sisyphus), associatedToponym, Almones]
-
A.
isToponymOf
Indicates that one entity is a place name (toponym) that refers to the location represented by the other entity.
-
B.
hasToponymicAssociation
chosen
Indicates a relationship where one entity is associated with, derived from, or named after a particular place or geographic name (toponym).
-
C.
legacyToponym
Indicates that one place name is an older or former name historically used to refer to the same geographic entity as another place name.
-
D.
hasNotableToponym
Indicates that an entity is associated with a place name that is particularly notable, distinctive, or significant.
-
E.
toponymRefersTo
Indicates that a place name (toponym) designates or refers to a specific geographic entity or location.
- F. None of above.
Provenance (3 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 18, 2026, 6:23 a.m.