Triple
T4273318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enya |
E96987
|
entity |
| Predicate | hasPerformedLiveIn |
P55120
|
FINISHED |
| Object | very few concert tours |
—
|
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: very few concert tours | Statement: [Enya, hasPerformedLiveIn, very few concert tours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformedLiveIn Context triple: [Enya, hasPerformedLiveIn, very few concert tours]
-
A.
hasNotableLivePerformancesBy
Indicates that an entity (such as a work, event, or venue) is associated with notable live performances given by a specified performer or group.
-
B.
hasFanPerformances
Indicates that an entity has associated performances created or carried out by fans.
-
C.
recordedAsLive
Indicates that an audio or video performance was captured in real time before an audience or in a live setting, rather than produced or edited in a studio environment.
-
D.
hasLiveMusic
Indicates that a place or event features live musical performances as part of its offerings.
-
E.
hasLiveAlbum
Indicates that an artist or musical act has released at least one live album recording.
- 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_69b34544be3c819084d1ab82d29f90c5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34ffe44508190875d734eb18dfb87 |
completed | March 12, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69b347faa45481908c19c29fb906dc92 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e0606488190baadf469a1afc3c2 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:07 p.m.