Triple
T21723702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conga |
E536223
|
entity |
| Predicate | hasRadioEditLength |
P145098
|
FINISHED |
| Object | 4:14 |
—
|
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: 4:14 | Statement: [Conga, hasRadioEditLength, 4:14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRadioEditLength Context triple: [Conga, hasRadioEditLength, 4:14]
-
A.
hasRadioEdit
Indicates that an entity has an associated radio-friendly edited version of itself.
-
B.
hasRadio
Indicates that an entity is equipped with or includes a radio device.
-
C.
singleEditLength
Indicates that one entity can be transformed into the other by performing exactly one edit operation (insertion, deletion, or substitution).
-
D.
isRadioFriendly
Indicates that something (typically a song, track, or audio content) is suitable for broadcast on mainstream radio, usually by meeting content, length, and formatting standards.
-
E.
numberOfRadios
Indicates the quantity of radios associated with a given entity.
- 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd97150c08190861bdc35416665a9 |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:48 p.m.