Triple
T30498866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All People That on Earth Do Dwell |
E776081
|
entity |
| Predicate | typicalTune |
P115912
|
FINISHED |
| Object | Old 100th |
E1917135
|
NE 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: Old 100th | Statement: [All People That on Earth Do Dwell, typicalTune, Old 100th]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTune Context triple: [All People That on Earth Do Dwell, typicalTune, Old 100th]
-
A.
oftenTunesTo
Indicates that one entity frequently adjusts or sets its frequency, settings, or focus to match or receive another entity.
-
B.
notableTune
Indicates that a tune is especially significant, well-known, or characteristic in relation to a particular entity.
-
C.
commonlySungTune
chosen
Indicates that a particular tune is frequently used as the melody for singing a given piece (such as lyrics, a song, or text).
-
D.
typicalChord
Indicates that a chord is a standard, commonly occurring, or characteristic instance within a given musical or harmonic context.
-
E.
typicalCadenzasBy
Indicates that a particular cadenza is characteristically or commonly composed or used by a given musician or composer.
- F. None of above.
Provenance (4 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a27be692f5c8190af43013bf3bc0e57 |
completed | June 9, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:14 p.m.