Triple
T34452432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motown M-772L |
E884409
|
entity |
| Predicate | usedOnOriginalIssue |
P179737
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Motown M-772L, usedOnOriginalIssue, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedOnOriginalIssue Context triple: [Motown M-772L, usedOnOriginalIssue, yes]
-
A.
isOriginalIssueNumber
Indicates that a given issue identifier corresponds to the first or primary publication number assigned to that issue, rather than a reprint, variant, or subsequent numbering.
-
B.
isOriginalIssueOf
Indicates that one item is the first or primary issue/edition from which another related issue or edition derives.
-
C.
originUse
Indicates that one entity is used as the original source, basis, or starting point for the creation, derivation, or use of another entity.
-
D.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
E.
possibleOriginalReference
Indicates that one entity may be the source, inspiration, or earlier version from which another entity is derived or referenced.
- F. None of above. chosen
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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
| PDg | Predicate description generation | batch_69f727bd39b081908457590c3ba9b745 |
completed | May 3, 2026, 10:47 a.m. |
Created at: May 1, 2026, 2 a.m.