Triple
T34452420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motown M-772L |
E884409
|
entity |
| Predicate | labelCodeFor |
P8090
|
FINISHED |
| Object | Touch Me in the Morning |
—
|
NE NERFINISHED |
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: Touch Me in the Morning | Statement: [Motown M-772L, labelCodeFor, Touch Me in the Morning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: labelCodeFor Context triple: [Motown M-772L, labelCodeFor, Touch Me in the Morning]
-
A.
labelCodeType
Indicates that one entity serves as the type or classification scheme for the labeling code applied to another entity.
-
B.
labelCodePosition
Indicates assigning a specific label to a particular position or location within a code sequence or code structure.
-
C.
catalogCode
chosen
Indicates that an entity is assigned a specific catalog identifier or code used for classification or reference.
-
D.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
E.
labelOf
Indicates that one entity serves as the name, tag, or identifying label assigned to another entity.
- 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71974786c8190a34dc79fc344d167 |
completed | May 3, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2 a.m.