Triple
T27618527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Lagan Love |
E700504
|
entity |
| Predicate | setToTraditionalAir |
P162757
|
FINISHED |
| Object | traditional Irish air |
—
|
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: traditional Irish air | Statement: [My Lagan Love, setToTraditionalAir, traditional Irish air]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setToTraditionalAir Context triple: [My Lagan Love, setToTraditionalAir, traditional Irish air]
-
A.
settingTraditional
Indicates that something is situated or occurs within a traditional setting, context, or environment.
-
B.
isTraditional
Indicates that something adheres to long-established customs, practices, or norms rather than modern or innovative ones.
-
C.
replacedTraditionalName
Indicates that one name has taken the place of, or superseded, an earlier traditional name for the same entity.
-
D.
isTraditionalInCountry
Indicates that something is customary, long-established, or commonly practiced within a particular country.
-
E.
hasTraditionalDirection
Indicates that something is associated with or oriented according to a customary or historically established direction.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f630d9c4ec8190af57c75c41ac5b05 |
completed | May 2, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62d14c24c81909e86678c1b5fd429 |
completed | May 2, 2026, 4:57 p.m. |
Created at: April 27, 2026, 2:13 p.m.