Triple
T23900066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yola language of County Wexford |
E601016
|
entity |
| Predicate | hasPoeticAttestations |
P154001
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Yola language of County Wexford, hasPoeticAttestations, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoeticAttestations Context triple: [Yola language of County Wexford, hasPoeticAttestations, yes]
-
A.
hasPoeticEpigraphs
Indicates that one entity (typically a work) includes poetic epigraphs associated with or prefacing another entity.
-
B.
hasPoeticLyrics
Indicates that something (such as a song, text, or speech) contains lyrics or wording that are artistic, expressive, or characteristic of poetry.
-
C.
hasPoeticSpeaker
Indicates that one entity functions as the poetic speaker or voice expressing the content of another entity (such as a poem or lyrical work).
-
D.
hasCanonicalPoem
Indicates that an entity is associated with a poem recognized as its standard or authoritative version.
-
E.
hasPoeticVoice
Indicates that one entity possesses or exhibits the distinctive poetic style, tone, or expressive voice associated with another entity.
- F. None of above. chosen
Provenance (4 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cdddca088190b6c26df984a143ad |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 8:26 p.m.