Triple
T33797987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One Song to the Tune of Another |
E866127
|
entity |
| Predicate | isSegmentType |
P2563
|
FINISHED |
| Object | game round |
—
|
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: game round | Statement: [One Song to the Tune of Another, isSegmentType, game round]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSegmentType Context triple: [One Song to the Tune of Another, isSegmentType, game round]
-
A.
hasSegmentType
chosen
Indicates that an entity is associated with, or classified by, a particular type or category of segment within a larger structure or sequence.
-
B.
appliesToSegmentType
Indicates that a rule, condition, or operation is specifically associated with and relevant to a particular type of segment.
-
C.
isSectionOfType
Indicates that a given section belongs to, or is categorized as, a specific predefined type.
-
D.
isSpaceSegmentOf
Indicates that one spatial region or segment is a constituent part or subdivision of a larger spatial extent or segment.
-
E.
isSegmentedName
Indicates that a name is composed of multiple distinct segments or parts, typically separated or parsed according to specific rules.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:46 a.m.