Triple
T18696072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teucer |
E457117
|
entity |
| Predicate | cultOrLegend |
P74718
|
FINISHED |
| Object | reputed founder of Salamis in Cyprus |
—
|
LITERAL 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: reputed founder of Salamis in Cyprus | Statement: [Teucer, cultOrLegend, reputed founder of Salamis in Cyprus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultOrLegend Context triple: [Teucer, cultOrLegend, reputed founder of Salamis in Cyprus]
-
A.
famousLegend
Indicates that the subject is widely known and celebrated in stories, myths, or folklore, often with enduring cultural significance.
-
B.
associatedLegendaryFigure
chosen
Indicates that an entity is traditionally linked or connected to a particular legendary or mythological figure.
-
C.
featuresCreatureOrLegend
Indicates that something includes, depicts, or prominently involves a particular creature or legendary being.
-
D.
bestKnownLegend
Indicates that one entity is the most prominent or widely recognized legendary story or myth associated with another entity.
-
E.
hasNameInReligionOrFolklore
Indicates that an entity is known by a particular name specifically within a religious or folkloric tradition.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562e775408190996b4c613b83f185 |
completed | April 19, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.