Triple
T38138244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simon & Garfunkel discography |
E952406
|
entity |
| Predicate | hasSinglesCount |
P76841
|
FINISHED |
| Object | more than 20 |
—
|
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: more than 20 | Statement: [Simon & Garfunkel discography, hasSinglesCount, more than 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSinglesCount Context triple: [Simon & Garfunkel discography, hasSinglesCount, more than 20]
-
A.
numberOfSingles
chosen
Indicates the count of individual single items (such as single tracks, units, or occurrences) associated with a given entity.
-
B.
includesSinglesFrom
Indicates that a collection or group contains individual single items originating from a specified source or set.
-
C.
hasSingle
Indicates that an entity possesses exactly one instance of a specified related entity or attribute.
-
D.
isSingleFromArtistCatalog
Indicates that a musical work is a single that originates from or is included in an artist's catalog.
-
E.
hasPitchCount
Indicates that an entity is associated with a specific number of pitches, representing how many pitches have occurred or been recorded for it.
- 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_69f76f09a7148190a4b91c0bacdc127a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: May 3, 2026, 4:21 p.m.