Triple
T14612160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rodgers and Hammerstein revival cast recordings |
E342987
|
entity |
| Predicate | typicalTrackContent |
P9638
|
FINISHED |
| Object | overtures |
—
|
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: overtures | Statement: [Rodgers and Hammerstein revival cast recordings, typicalTrackContent, overtures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTrackContent Context triple: [Rodgers and Hammerstein revival cast recordings, typicalTrackContent, overtures]
-
A.
typicalItem
Indicates that an item is a representative or characteristic example of a broader category, class, or set.
-
B.
trackType
Indicates the specific kind or category of track associated with an entity, such as its functional or physical classification.
-
C.
typicalSegmentType
chosen
Indicates that something is classified as belonging to a usual or characteristic type of segment within a broader structure or sequence.
-
D.
tracks
Indicates that one entity monitors, follows, or keeps a record of another entity’s state, behavior, or progress over time.
-
E.
typicalTrackLengthRange
Indicates the usual minimum and maximum lengths that a track associated with something tends to fall between.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb450e6588190a94488d8e71888c8 |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.