Triple
T18267478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opry |
E437519
|
entity |
| Predicate | hasRegularSegmentType |
P109707
|
FINISHED |
| Object | live musical performance |
—
|
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: live musical performance | Statement: [Opry, hasRegularSegmentType, live musical performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegularSegmentType Context triple: [Opry, hasRegularSegmentType, live musical performance]
-
A.
hasRegularSegment
chosen
Indicates that an entity includes or is associated with a segment that occurs in a consistent, repeating, or standard pattern.
-
B.
hasSegmentType
Indicates that an entity is associated with, or classified by, a particular type or category of segment within a larger structure or sequence.
-
C.
hasTypicalSegmentNumber
Indicates that an entity is characterized by a usual or standard number of segments it possesses.
-
D.
hasSegmentWith
Indicates that an entity contains or includes at least one segment that satisfies a specified condition or matches a given segment.
-
E.
hasSegmentOn
Indicates that one entity includes or occupies a specific segment or portion on another entity (such as a line, path, 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ff7bda5c8190a5a85f3cfb7aa4ef |
completed | April 19, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.