Triple
T5863286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ultraviolet (Light My Way) |
E130325
|
entity |
| Predicate | hasNotableLiveUse |
P5773
|
FINISHED |
| Object | performed on U2 360° Tour |
—
|
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: performed on U2 360° Tour | Statement: [Ultraviolet (Light My Way), hasNotableLiveUse, performed on U2 360° Tour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableLiveUse Context triple: [Ultraviolet (Light My Way), hasNotableLiveUse, performed on U2 360° Tour]
-
A.
notableUse
chosen
Indicates that something is prominently or famously used by a particular entity, context, or for a specific purpose.
-
B.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
-
C.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
D.
stillUsedBy
Indicates that something continues to be used or relied upon by another entity at the present time.
-
E.
hasNotableNative
Indicates that an entity is known for having a notable person, species, or element that originates from or is native to it.
- 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_69c0084f3bb08190a7720f55f7aa4252 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03345ca0c819081c81148d054fed2 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:56 p.m.