Triple
T31430921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Little Less Conversation (Elvis vs JXL remix) |
E801794
|
entity |
| Predicate | lengthExtended |
P266
|
FINISHED |
| Object | 6:00 |
—
|
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: 6:00 | Statement: [A Little Less Conversation (Elvis vs JXL remix), lengthExtended, 6:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lengthExtended Context triple: [A Little Less Conversation (Elvis vs JXL remix), lengthExtended, 6:00]
-
A.
extensionLength
Indicates the length or magnitude of an extension from a reference point or base object.
-
B.
length
chosen
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
-
C.
extendedIn
Indicates that one entity continues, prolongs, or expands the scope, duration, or range of another entity.
-
D.
plannedExtensionLength
Indicates the intended or proposed length of an extension as specified in a plan or design.
-
E.
wasExtendedTo
Indicates that something previously existing was lengthened, expanded, or prolonged to reach a new limit, scope, or duration.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 8:57 p.m.