Triple
T25159911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hope for Haiti Now telethon |
E626407
|
entity |
| Predicate | featuredSegmentType |
P57060
|
FINISHED |
| Object | musical performances |
—
|
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: musical performances | Statement: [Hope for Haiti Now telethon, featuredSegmentType, musical performances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredSegmentType Context triple: [Hope for Haiti Now telethon, featuredSegmentType, musical performances]
-
A.
featuresSegment
Indicates that one entity includes or highlights a particular segment or portion of another entity as a notable part of it.
-
B.
notableSegmentType
Indicates that a particular segment or portion of something is classified as being of notable or special significance by its type.
-
C.
featuredElement
Indicates that one element is highlighted or given special prominence relative to others in a given context.
-
D.
featuredContentType
chosen
Indicates the specific type or category of content that is highlighted or promoted as featured.
-
E.
typicalSegmentType
Indicates that something is classified as belonging to a usual or characteristic type of segment within a broader structure or sequence.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 18, 2026, 6:31 a.m.